-
Notifications
You must be signed in to change notification settings - Fork 593
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
Fixed taking snapshot in rm_stm
#12155
Conversation
Any other backports required here? |
/ci-repeat 4 |
1 similar comment
/ci-repeat 4 |
/ci-repeat 4 |
1 similar comment
/ci-repeat 4 |
/ci-repeat 1 |
When snapshot is applied on startup by the persisted stm it should not be the stm implementer responsibility to store `_last__snapshot_offset`. Signed-off-by: Michal Maslanka <michal@redpanda.com>
Signed-off-by: Michal Maslanka <michal@redpanda.com>
/ci-repeat 1 |
ci failure: #12275 |
/backport v23.2.x |
/backport v23.1.x |
Failed to run cherry-pick command. I executed the commands below:
|
This change fixes an issue where a snapshot might
have been created with offset lower from the offset of a snapshot that
was already applied.
Fixes: #11659
Backports Required
Release Notes
Improvements
rm_stm