Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
Replication
-
ALL
Description
For example, say a node with member id 2 in the config crashes. The data is restored from backup taken a day prior and restarted. Now the node begins reporting upstream for id 2 a position that is behind where id 2 had previously reported.
Today's position managing code does not change a node's position if it is reported to have moved backward.
This is a problem because nodes can thus appear to contain data that they do not actually have.
Attachments
Issue Links
- is documented by
-
DOCS-15225 Document risks of node rejoining a cluster with staler data than before
-
- Backlog
-
- is related to
-
SERVER-17934 Do not report upstream progress while in state STARTUP2
-
- Closed
-
-
SERVER-18511 Report upstream progress when initial sync completes
-
- Closed
-
- related to
-
SERVER-46085 Fail initial sync attempt if sync source is in initial sync
-
- Closed
-