Skip to content
This repository was archived by the owner on Sep 26, 2024. It is now read-only.

Make delayed fetch request timeout configurable#2

Merged
dopuskh3 merged 2 commits intotsfrom
tiered-storage-timeout
Jan 24, 2024
Merged

Make delayed fetch request timeout configurable#2
dopuskh3 merged 2 commits intotsfrom
tiered-storage-timeout

Conversation

@dopuskh3
Copy link
Copy Markdown

This is PR pull the change in here apache#14778, rebase it on top of 3.7.

This add a broker configuration to configure the max remote fetch wait time.

dopuskh3 and others added 2 commits January 24, 2024 10:38
remote.log.reader.fetch.timeout.ms, default is 2s
…elayedRemoteFetch

DelayedRemoteFetch uses `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.
@dopuskh3 dopuskh3 merged commit ea42ea0 into ts Jan 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants