Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unoptimization in _list APIs leading to unnecessary IndicesStats call #16448

Closed
gargharsh3134 opened this issue Oct 23, 2024 · 0 comments · Fixed by #16444
Closed

Unoptimization in _list APIs leading to unnecessary IndicesStats call #16448

gargharsh3134 opened this issue Oct 23, 2024 · 0 comments · Fixed by #16444
Labels
bug Something isn't working Cluster Manager

Comments

@gargharsh3134
Copy link
Contributor

gargharsh3134 commented Oct 23, 2024

Describe the bug

For paginated _list/indices and _list/shards APIs, if their corresponding strategies don't output any entities, the indicesToBeQueried gets set to empty and any subsequent IndicesStatsTransport action ends up fetching stats for all the indices. This defeats the purpose of pagination to avoid fetching stats for all the indices at once.

Related component

Cluster Manager

To Reproduce

Query _list/indices API with a wildcard pattern which doesn't match any index. PaginationStrategy would not output any index to be fetched but notice IndicesStats call being made for all the indices in the cluster.

Expected behavior

Request IndicesStats only for the required set of indices.

Additional Details

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Cluster Manager
Projects
Status: ✅ Done
2 participants