KAFKA-19952: When remote storage keep outage status. the local segment never get deleted #21049
Conversation
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
github-actions
bot
added
triage
…t never get deleted Signed-off-by: jiafu1115 <[email protected]>
jiafu1115
force-pushed
the
protectedStorage
branch
from
f2a13df to
087a563
Compare
jiafu1115
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Test Case:
Topic enable remote storage:
Local retention time: 10 minutes
Remote retenton time: 20 minutes
Keep run producer to send. and pick one time after 20 minutes to set the AWS S3 permisssion to let the remote upload fail.
After 1 hour. you will see the local segments keep increase and save about 1 hours even the both local/remote retention time < 20 minutes.
So we need one protect for this case to avoid the local disk keep increase forever util the outage recovered.