[v23.2.x] cloud_storage: fix segment materialisation race #13823
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
In order to create a new materialised segment, one needs to grab units from `materialized_resources` first. This is an async operation. By the time units are acquired, said segment might have already been via a different code path, resulting in the assertion in `remote_partition::materialize_segment` triggering. `remote_partition::aborted_transactions` was particularly susceptible to this. This patch fixes the issue by checking for the existence of the segment and creating a segment (if needed) in the same scheduling task. Functionally, for the read path, nothing should change. (cherry picked from commit 3100f40)
piyushredpanda
approved these changes
Sep 29, 2023
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.
Backport of PR #13796