You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
Today, the cat indices API does not support overall timeouts or per-node transport request timeouts. In the event of a faulty node, the API can become unresponsive, and in a heavily loaded cluster, the API may take longer than expected to respond. It is essential to implement timeout support for the cat indices API.
Describe the solution you'd like
Recently, we added cancellation support for the cat shards API, which allows us to specify an overall timeout for the API. Additionally, there are some APIs that support a per-node transport request timeout, such as cat/nodes. This enhancement addresses both issues mentioned above.
Related component
Cluster Manager
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
aasom143
changed the title
[Feature Request] <Cancellation support for cat/indices API>
[Feature Request] Cancellation support for cat/indices API.
Sep 6, 2024
Is your feature request related to a problem? Please describe
Today, the cat indices API does not support overall timeouts or per-node transport request timeouts. In the event of a faulty node, the API can become unresponsive, and in a heavily loaded cluster, the API may take longer than expected to respond. It is essential to implement timeout support for the cat indices API.
Describe the solution you'd like
Recently, we added cancellation support for the cat shards API, which allows us to specify an overall timeout for the API. Additionally, there are some APIs that support a per-node transport request timeout, such as cat/nodes. This enhancement addresses both issues mentioned above.
Related component
Cluster Manager
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: