Currently we dont have a set timeout limit defined for the mapper so it falls back to its default.
This is also not properly handled within the mapper as the in flight requests are still executed even if the client connection has been terminated.
We need to add a config option for defining the timeout limit of the mapper, and when this timeout is reached we need to kill all in flight requests and respond back to the client with a timeout message
Currently we dont have a set timeout limit defined for the mapper so it falls back to its default.
This is also not properly handled within the mapper as the in flight requests are still executed even if the client connection has been terminated.
We need to add a config option for defining the timeout limit of the mapper, and when this timeout is reached we need to kill all in flight requests and respond back to the client with a timeout message