-
Notifications
You must be signed in to change notification settings - Fork 614
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
storage: remove assertion on is_cloud_retention_active
#23936
Conversation
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
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/57240#0192d53e-9405-4551-aaa8-13685ac95830:
|
Retry command for Build#57240please wait until all jobs are finished before running the slash command
|
/ci-repeat 4 |
the below tests from https://buildkite.com/redpanda/redpanda/builds/57345#0192db79-8dcd-43bc-9004-f2ee4667d1cf have failed and will be retried
|
This assertion can be triggered if a the configuration for a topic is changed between when space management sets the `_cloud_gc_offset` to when gc actually runs on the log. So to avoid crashing in this case the assertion is changed to an early return and a warning is logged instead.
09cb1f5
to
137951e
Compare
The tests had previously failed either due to being flake-y or for infra issues. I've rebased this branch and am re-running the tests. Assuming all pass this should be good to merge. |
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/57889#01931b96-6ffa-4783-a909-2d3c7d316365 |
/backport v24.2.x |
/backport v24.1.x |
/backport v23.3.x |
This assertion can be triggered if a the configuration for a topic is changed between when space management sets the
_cloud_gc_offset
to when gc actually runs on the log. So to avoid crashing in this case the assertion is changed to an early return and a warning is logged instead.Fixes CORE-8070
Backports Required
Release Notes