RDoc-3818 - Document responsible-node and grace-period behavior for backup tasks - #2459
Merged
Conversation
efratshenhar
reviewed
Jun 7, 2026
|
|
||
| When the current responsible node enters the `Rehab` state, | ||
| the cluster observer waits a configurable grace period (30 minutes by default) | ||
| before moving the task to another node. |
There was a problem hiding this comment.
An exception is a task pinned to its mentor node (PinToMentorNode),
which is not reassigned while the node remains in the database group.
Contributor
Author
There was a problem hiding this comment.
added clarifications in backup/faq and highly available tasks pages
| Instead, it waits a grace period (30 minutes by default) before reassigning the task | ||
| to another database-group member. | ||
| The grace period gives the original node a chance to recover, | ||
| and prevents the same backup from running on two nodes at once. |
There was a problem hiding this comment.
Worth mentioning the pinned case here — a pinned task behaves differently from what this section implies:
If the task is **pinned** to its mentor node (PinToMentorNode), it is not reassigned as long as that node remains in the database group — even while in Rehab, and even after the grace period expires. It is only moved to another node if the pinned node is removed from the database group.
…AQ and `highly available tasks` pages
efratshenhar
approved these changes
Jun 10, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue link
RDoc-3818
Additional description
Document backup behavior: cluster node can start backup while another cluster node already runs backup
Type of change
/templatesor readme)Changes in docs URLs
/scripts/redirects.jsonfile, setDocuments MovedPR label)Changes in UX/UI