[DOCS-15225] Document risks of node rejoining a cluster with staler data than before Created: 11/Apr/22 Updated: 22/Jan/24 |
|
| Status: | Backlog |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | backlog, feature, quick-win, replication, server-docs-bug-bash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 25 weeks, 1 day ago | ||||||||
| Description |
|
Restoring from a backup or resyncing from a stale node comes with the risk of a node being staler than it used to be in a replica set. We should document these risks so that users are aware of what could go wrong and can make use of better practices to try to avoid this from happening. |
| Comments |
| Comment by Samyukta Lanka [ 16/Aug/22 ] |
|
I think this is relevant to all users restoring from a backup, regardless of Atlas vs on-prem. |
| Comment by Ashley Brown [ 11/Aug/22 ] |
|
Hey samy.lanka@mongodb.com, is this relevant to Atlas users or only to on-prem users? |