-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Expose node weights in GetDesiredBalance API response #126579
Copy link
Copy link
Closed
Labels
:Distributed/AllocationAll issues relating to the decision making around placing a shard (both master logic & on the nodes)All issues relating to the decision making around placing a shard (both master logic & on the nodes)>enhancementSupportabilityImprove our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Team:Distributed Coordination (obsolete)Meta label for Distributed Coordination team. Obsolete. Please do not use.Meta label for Distributed Coordination team. Obsolete. Please do not use.
Metadata
Metadata
Assignees
Labels
:Distributed/AllocationAll issues relating to the decision making around placing a shard (both master logic & on the nodes)All issues relating to the decision making around placing a shard (both master logic & on the nodes)>enhancementSupportabilityImprove our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.Team:Distributed Coordination (obsolete)Meta label for Distributed Coordination team. Obsolete. Please do not use.Meta label for Distributed Coordination team. Obsolete. Please do not use.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Currently the GetDesiredBalance reports
shard_count,forecast_write_loadandforecast_disk_usagewhich are components of thenode_weight. It would be great if we also report the actualnode_weightdirectly 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
DesiredBalancesince #115854