mvcc: fix watch compaction race causing double notifications #21189
+19
−6
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.
This PR documents and fixes a correctness issue in the watch compaction path.
Issue
When the number of unsynced watchers was below the sync limit,
choose()returned the original watcher group instead of a copy. During compaction, this caused the watcher map to be modified while it was being iterated, which could lead to:removing missing watcher!This can occur during normal operation with auto-compaction enabled.
Fix
choose()now always returns a copy of the watcher groupchooseAll()no longer deletes watchers while iteratingsyncWatchers()Result
The fix eliminates panics and silent watch failures while preserving existing behavior.
All relevant MVCC tests pass, including compaction-related watch tests.