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

[META] Optimise shard allocation decider execution times #15872

Open
Bukhtawar opened this issue Sep 9, 2024 · 0 comments
Open

[META] Optimise shard allocation decider execution times #15872

Bukhtawar opened this issue Sep 9, 2024 · 0 comments
Labels
Meta Meta issue, not directly linked to a PR

Comments

@Bukhtawar
Copy link
Collaborator

Bukhtawar commented Sep 9, 2024

Please describe the end goal of this project

The shard placement logic is executed on a single threaded cluster manager's state execution thread. For larger clusters this might cause the execution times to go beyond a minute thereby causing critical operations like index creation and settings update etc to starve making the cluster unmanageable

Supporting References

Related PRs

  1. Caching avg total bytes and avg free bytes inside ClusterInfo #14851
  2. Removing unnecessary List.removeAll from LocalShardsBalancer to filter remote search shard from relocation decision #14613
  3. Optimising hashmap.get call inside AwarenessAllocationDecider #14761
  4. Removing String format in RemoteStoreMigrationAllocationDecider #14612
  5. Offline calculation of total shard across all node and caching it for weight calculation inside LocalShardBalancer #14675
  6. Cache index shard limit to optimise ShardLimitsAllocationDecider #14962
  7. Skip unnecessary string format in ThrottlingAllocationDecider when not in debug mode #13750

Issues

TBD

Related component

Cluster Manager

@Bukhtawar Bukhtawar added Meta Meta issue, not directly linked to a PR untriaged labels Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Meta Meta issue, not directly linked to a PR
Projects
Status: New
Development

No branches or pull requests

1 participant