-
Notifications
You must be signed in to change notification settings - Fork 470
Update docs for Leader Leases GA in v25.2 #19587
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
Conversation
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
a298691
to
11a4b6d
Compare
Fixes DOC-11671, DOC-12861 Summary of changes: - Update 'Architecture > Replication Layer > Leader Leases' to remove the stuff about them being off by default - While we're in there, also update the 'How leases are transferred off a dead node' section to match the new reality. Also did various other edits on that page re: leaseholder vs. Raft leader mismatches which won't exist anymore - Revise 'Troubleshoot Self-Hosted Setup > Node liveness issues' so that the content there stops referring to Ye Olde SPOF liveness range - Update many, many other places where we said things like "sometimes the leaseholder and the Raft leader are different, and that can be sad, but usually they aren't" etc. that no longer apply - Attempt to rebrand the old "node liveness" stuff as "node heartbeats" in a few places and clarify that it is only used for a couple of less central purposes like cluster membership, etc., in v25.2+ - Also remove lots of extemporaneous mentions of "node liveness heartbeats" etc. from various places where it was sprinkled around. - Also remove various references to range quiescence, which is not a thing for Leader leases
11a4b6d
to
e61c059
Compare
hi @arulajmani @miraradeva @iskettaneh ! in addition to what I wrote in the PR description describing the high level changes, I also sprinkled some 'xxx' broken links in here where I had specific questions. Commonly, these are things like places in the DB Console that still talk about "node liveness" etc (at least as of the beta.3 which is still the most recent available release). Often it's asking if we can/should just delete these things? or add some words around "oh this is semi-obsolete, look at Leader Leases instead". thanks! |
src/current/_includes/v25.2/leader-leases-node-heartbeat-use-cases.md
Outdated
Show resolved
Hide resolved
src/current/_includes/v25.2/known-limitations/per-replica-circuit-breaker-limitations.md
Show resolved
Hide resolved
@miraradeva and @iskettaneh i've tried to address your comments to hopefully get us closer, this is RFAL |
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! Thanks for the multiple revisions!
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! Mostly style nits, but one place where it sounded like the Raft leader was still described as 'sometimes' also being the leaseholder
Fixes DOC-11671, DOC-12861
Summary of changes:
Update 'Architecture > Replication Layer > Leader Leases' to remove the
stuff about them being off by default
off a dead node' section to match the new reality.
Revise 'Troubleshoot Self-Hosted Setup > Node liveness issues'