Skip to content
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

cherrypick-2.0: storage: Don't allow node liveness expiration to move backwards #23122

Merged

Conversation

bdarnell
Copy link
Contributor

This ensures that if the system clock moves backwards while the
cockroach process is not running, the node will not be able to
become live until the clock has caught up with its previous value.
If it did, it would be possible to serve stale reads.

Release note (bug fix): Guard against stale reads caused by the system
clock moving backwards while the cockroach process is not running.

This ensures that if the system clock moves backwards while the
`cockroach` process is not running, the node will not be able to
become live until the clock has caught up with its previous value.
If it did, it would be possible to serve stale reads.

Release note (bug fix): Guard against stale reads caused by the system
clock moving backwards while the `cockroach` process is not running.
@bdarnell bdarnell requested a review from a team February 26, 2018 22:42
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@bdarnell bdarnell merged commit c703f82 into cockroachdb:release-2.0 Feb 27, 2018
@bdarnell bdarnell deleted the cherrypick-liveness-backwards branch February 27, 2018 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants