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
KAFKA-15410: Delete records with tiered storage integration test (4/4) #14330
Conversation
5117f77
to
a6ba58a
Compare
...org/apache/kafka/tiered/storage/integration/DeleteSegmentsDueToLogStartOffsetBreachTest.java
Outdated
Show resolved
Hide resolved
@clolov @divijvaidya @showuon @abhijeetk88 @satishd Call for review. Please take a look when you get chance! |
...org/apache/kafka/tiered/storage/integration/DeleteSegmentsDueToLogStartOffsetBreachTest.java
Outdated
Show resolved
Hide resolved
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.
Thanks @kamalcph for the PR. Left a few comments.
...org/apache/kafka/tiered/storage/integration/DeleteSegmentsDueToLogStartOffsetBreachTest.java
Show resolved
Hide resolved
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.
Thank you for the changes, they make sense to me!
...org/apache/kafka/tiered/storage/integration/DeleteSegmentsDueToLogStartOffsetBreachTest.java
Outdated
Show resolved
Hide resolved
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.
LGTM! Just one minor comment. Thanks for adding the tests.
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.
Thanks @kamalcph for addressing the review comments. I have one last comment.
return false; | ||
}); | ||
if (isSegmentDeleted) { | ||
remainingBreachedSize = retentionSizeData.isPresent() ? |
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.
It seems we should not change remainingBreachedSize
as that is computed only with the segments that are in the current leader epoch lineage. This is the change/fix that you had putup in earlier.
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.
Good point! Addressed your review comment. PTAL.
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.
Thanks @kamalcph for addressing the review comments. LGTM.
…on test. - Relax the segment validation checks while deleting the remote log segments.
…tart-offset breach
cadec0a
to
ff4dbf0
Compare
There are a few test failures unrelated to this change. Merging it to trunk and 3.6. |
#14330) * Added the integration test for DELETE_RECORDS API for tiered storage enabled topic * Added validation checks before removing remote log segments for log-start-offset breach Reviewers: Satish Duggana <satishd@apache.org>, Luke Chen <showuon@gmail.com>, Christo Lolov <lolovc@amazon.com>
Will look into it later today. |
Opened #14439 to fix this flaky test. |
apache#14330) * Added the integration test for DELETE_RECORDS API for tiered storage enabled topic * Added validation checks before removing remote log segments for log-start-offset breach Reviewers: Satish Duggana <satishd@apache.org>, Luke Chen <showuon@gmail.com>, Christo Lolov <lolovc@amazon.com>
Added the integration test for
DELETE_RECORDS
API for tiered storage enabled topic.Committer Checklist (excluded from commit message)