Skip to content

Conversation

@DiannaHohensee
Copy link
Contributor

@DiannaHohensee DiannaHohensee commented Jan 27, 2025

This service is added to the desired balance allocator to track and
report on balancer round activity. It is a WIP and currently only
tracks the number of shard moves caused by a balancing round.
Reporting balancer round summary results will provide information
with which to do cost-benefit analyses of the work that shard
allocation rebalancing executes. It is disabled by default.

Relates ES-10341

@DiannaHohensee DiannaHohensee added >enhancement :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) Team:Distributed Coordination Meta label for Distributed Coordination team labels Jan 27, 2025
@DiannaHohensee DiannaHohensee self-assigned this Jan 27, 2025
@DiannaHohensee DiannaHohensee requested a review from a team as a code owner January 27, 2025 19:58
This service is added to the desired balance allocator
to track and report on balancer round activity. It is
a WIP and currently only tracks the number of shard
moves caused by a balancing round. Reporting balancer
round summary results will provide information with
which to do cost-benefit analyses of the work that
shard allocation rebalancing executes.
@elasticsearchmachine
Copy link
Collaborator

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

@DiannaHohensee DiannaHohensee force-pushed the 2025/01/17/ES-10341-computation-metrics-pr branch from 4e0b59f to 42103ca Compare January 27, 2025 19:58
@elasticsearchmachine
Copy link
Collaborator

Hi @DiannaHohensee, I've created a changelog YAML for you.

@DiannaHohensee DiannaHohensee requested review from nicktindall and pxsalehi and removed request for a team January 27, 2025 21:12
public static final Setting<TimeValue> BALANCER_ROUND_SUMMARIES_LOG_INTERVAL_SETTING = Setting.timeSetting(
"cluster.routing.allocation.desired_balance.balanace_round_summaries_interval",
TimeValue.timeValueSeconds(10),
TimeValue.ZERO,
Copy link
Contributor

@nicktindall nicktindall Jan 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It says above

If less than zero, effectively disables reporting.

but the minimum is zero (I think?)

Either comment or code is out of date I think

Copy link
Contributor

@nicktindall nicktindall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor Author

@DiannaHohensee DiannaHohensee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching the details @nicktindall

@DiannaHohensee DiannaHohensee merged commit 623a6af into elastic:main Feb 3, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement Team:Distributed Coordination Meta label for Distributed Coordination team v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants