-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Fix non visible points during snapshots #7248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -969,6 +969,8 @@ impl SegmentHolder { | |
| log::trace!("Applying function on all proxied shard segments"); | ||
| let mut result = Ok(()); | ||
| let mut unproxied_segment_ids = Vec::with_capacity(proxies.len()); | ||
| // Reverse to unproxify first non-appendable segments | ||
| proxies.reverse(); | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I do not have a rock solid rational for this change, but it is necessary for the fix below to work properly |
||
| for (segment_id, proxy_segment) in &proxies { | ||
| // Get segment to snapshot | ||
| let op_result = match proxy_segment { | ||
|
|
@@ -997,13 +999,19 @@ impl SegmentHolder { | |
| } | ||
|
|
||
| // Try to unproxy/release this segment since we don't use it anymore | ||
| // Unproxying now lets us release the segment earlier, prevent unnecessary writes to the temporary segment | ||
| match Self::try_unproxy_segment(segments_lock, *segment_id, proxy_segment.clone()) { | ||
| Ok(lock) => { | ||
| segments_lock = lock; | ||
| unproxied_segment_ids.push(*segment_id); | ||
| // Unproxying now lets us release the segment earlier, prevent unnecessary writes to the temporary segment. | ||
| // Make sure to keep at least one proxy segment to maintain access to the points in the shared write segment. | ||
| // The last proxy and the shared write segment will be promoted into the segment_holder atomically | ||
| // by `Self::unproxy_all_segments` afterwards to maintain the read consistency. | ||
| let remaining = proxies.len() - unproxied_segment_ids.len(); | ||
| if remaining > 1 { | ||
| match Self::try_unproxy_segment(segments_lock, *segment_id, proxy_segment.clone()) { | ||
| Ok(lock) => { | ||
| segments_lock = lock; | ||
| unproxied_segment_ids.push(*segment_id); | ||
| } | ||
| Err(lock) => segments_lock = lock, | ||
| } | ||
| Err(lock) => segments_lock = lock, | ||
| } | ||
| } | ||
| proxies.retain(|(id, _)| !unproxied_segment_ids.contains(id)); | ||
|
|
||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we demote this to
trace?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to keep this way because double proxies are mysterious beasts.
Seeing it in the log is a clear sign that we are dealing with a complex situation like snapshot + optimizer.