-
Notifications
You must be signed in to change notification settings - Fork 34
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
fix(s3stream): compaction fix #506
Conversation
SCNieh
commented
Oct 30, 2023
•
edited
Loading
edited
- change copyAndWrite to readAndWrite in force split to reduce S3 API invocation
- limit memory consumption in force split
- separate force split and compaction into different commit request
1. wait for force split done before do WAL compaction 2. sanity check covers only compacted objects Signed-off-by: Shichao Nie <[email protected]>
The author of this PR, SCNieh, is not an activated member of this organization on Codecov. |
Qodana for JVM3 new problems were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at [email protected]
|
1. change copyAndWrite to readAndWrite in force split to reduce S3 API invocation 2. limit memory consumption in force split 3. separate force split and compaction into different commit request Signed-off-by: Shichao Nie <[email protected]>
Signed-off-by: Shichao Nie <[email protected]>
pair.getValue().completeExceptionally(ex); | ||
} | ||
return null; | ||
}).join(); |
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.
The join operation only makes prepareObject sequence.
…teration Signed-off-by: Shichao Nie <[email protected]>