Skip to content

Conversation

@schase-es
Copy link
Contributor

Backports the following commits to 9.1:

…lastic#137418)

In the DesiredBalanceAllocator, there are periodic log messages that warn of
long-running allocation balancing rounds. These track the number of loop
iterations and the amount of time passed since the last convergence, and log
when either exceeds a limit. A previous effort (4c979aa, elastic#100850) persisted
these metrics across compute runs so that a sequence of cluster state changes
did not disrupt these warnings. However, the modified time-based threshold
compares the current time against the last convergence, instead of the first
effort at recompute. If enough time has passed between balancing rounds, this
produces a warn-level message that misrepresents the round's compute time. This
change continues to include the time since last convergence, but uses the time
since compute began as the log threshold and as the time since resumption.

Fixes: ES-13327
@schase-es schase-es added :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >non-issue auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Distributed Coordination Meta label for Distributed Coordination team labels Dec 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >non-issue Team:Distributed Coordination Meta label for Distributed Coordination team v9.1.9

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants