Skip to content

Expose node weights in GetDesiredBalance API response #126579

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.

Sign up for GitHub

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

Jump to bottom
Open
ywangd opened this issue Apr 10, 2025 · 1 comment
Open

Expose node weights in GetDesiredBalance API response #126579

ywangd opened this issue Apr 10, 2025 · 1 comment
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement Supportability Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better. Team:Distributed Coordination Meta label for Distributed Coordination team

Comments

@ywangd
Copy link
Member

ywangd commented Apr 10, 2025

Currently the GetDesiredBalance reports shard_count, forecast_write_load and forecast_disk_usage which are components of the node_weight. It would be great if we also report the actual node_weight directly in the response to help investigation.

This may also be an opportunity to improve and consolidate the computation of individual weights since they might be already available in DesiredBalance since #115854
@ywangd ywangd added >enhancement :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) Supportability Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better. labels Apr 10, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Distributed Coordination Meta label for Distributed Coordination team label Apr 10, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement Supportability Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better. Team:Distributed Coordination Meta label for Distributed Coordination team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ywangd @elasticsearchmachine