Skip to content

Conversation

@untitaker
Copy link
Member

When rebalancing happens, segments get sharded into different queues
than before. Meaning that done_flush_segments tries to delete the "done"
key from the wrong queue. Pull through the queue_key to
done_flush_segments to fix that.

When rebalancing happens, segments get sharded into different queues
than before. Meaning that done_flush_segments tries to delete the "done"
key from the wrong queue. Pull through the queue_key to
done_flush_segments to fix that.
@untitaker untitaker requested a review from a team as a code owner April 4, 2025 10:21
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 4, 2025
@jan-auer jan-auer merged commit 73c708c into master Apr 4, 2025
48 checks passed
@jan-auer jan-auer deleted the fix/flush-rebalance branch April 4, 2025 11:12
andrewshie-sentry pushed a commit that referenced this pull request Apr 8, 2025
When rebalancing happens, segments get sharded into different queues
than before. Meaning that done_flush_segments tries to delete the "done"
key from the wrong queue. Pull through the queue_key to
done_flush_segments to fix that.
@github-actions github-actions bot locked and limited conversation to collaborators Apr 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants