c/distributed_kv_stm: prevent invalidated iterators during list #16421
Conversation
This file contains 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
The read lock held in `list` is for snapshots, and doesn't protect against concurrent writes. If we yield when copying the kv_data, then re-lookup the position we were at when resuming so that we don't access an invalidated iterator. Signed-off-by: Tyler Rockwood <rockwood@redpanda.com>
|
new failures in https://buildkite.com/redpanda/redpanda/builds/44572#018d62e8-fb2d-4fca-b622-d401ce1c568d: |
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.
The read lock held in
listis for snapshots, and doesn't protectagainst concurrent writes. If we yield when copying the kv_data, then
re-lookup the position we were at when resuming so that we don't access
an invalidated iterator.
FIXES: #16402
Backports Required
Release Notes
Bug Fixes