fix: prevent worker pool thrashing in cluster distribution layer#22
Merged
Conversation
distributeClusterTarget() sorted managers by live heartbeat worker counts, causing different per-host assignments each cycle even when the cluster-wide target was stable. Added distribution hysteresis: cache previous assignments and reuse them when the target, manager set, and per-host capacity are unchanged. Fresh computation only triggers on actual target changes, manager joins/leaves, or capacity constraint shifts. Closes #21 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes worker pool thrashing where
current_workersoscillated ±2 every few seconds despite a stable cluster-wide target. The autoscaler was killing and respawning workers in rapid succession due to sort-order instability in the distribution layer.distributeClusterTarget()sorted managers by live heartbeat worker counts ($currentCounts), which fluctuate tick-to-tick as workers spawn/die. Different sort orders produced different per-host assignments each cycle, even when the cluster-wide target was unchanged.Closes #21
Test plan
🤖 Generated with Claude Code