-
Notifications
You must be signed in to change notification settings - Fork 533
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
vsr: sync uses correct view to go into recovering_head
It might be the case that op_checkpoint: * is prepared in view X * is truncated in view X+1 * is committed in view X+2 When deciding whether to go into recovering_head state, the replica currently considers prepared view (checkpoint.header.view), and not the committed view. Use the correct view by: * Adding checkpoint's view into VSR State (but _not_ checkpoint state: different replicas might commit prepares at different views) * Populating that view from the message that informed us about the checkpoint target * this requires some intricate logic on pings, to make sure they indeed propagate correct view for checkpoint --- a replica accepts a checkpoint before it transitions to its view, and it should subsequently correctly propagate this higher view. This works because checkpoint view is also durable. Seed: 8593423301425288917 Closes: #1703
- Loading branch information
Showing
4 changed files
with
39 additions
and
16 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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