Description
We are reusing the fetch.max.wait.ms config as a delay timeout for DelayedRemoteFetchPurgatory. fetch.max.wait.ms purpose is to wait for the given amount of time when there is no data available to serve the FETCH request.
The maximum amount of time the server will block before answering the fetch request if there isn't sufficient data to immediately satisfy the requirement given by fetch.min.bytes.
Using the same timeout in the DelayedRemoteFetchPurgatory can confuse the user on how to configure optimal value for each purpose. Moreover, the config is of LOW importance and most of the users won't configure it and use the default value of 500 ms.
Having the delay timeout of 500 ms in DelayedRemoteFetchPurgatory can lead to higher number of expired delayed remote fetch requests when the remote storage have any degradation.
We should introduce one fetch.remote.max.wait.ms config (preferably server config) to define the delay timeout for DelayedRemoteFetch requests (or) take it from client similar to request.timeout.ms.
Attachments
Issue Links
- is a child of
-
KAFKA-15420 Kafka Tiered Storage V1
-
- Resolved
-
- links to
- mentioned in
-
Page Loading...