-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
-
(copied to CRM)
Maybe when mongodb trying to rollback data, after failover master,
trying and trying rollback again after it fails because of rollback limit (300mb current) is not a good idea.
"mongod" can not trying again if rollback fail because of limit.
After it restarted, it can trying rollback once again, but not more, or it can write this info to some collection and at start restore this information.
- is related to
-
SERVER-7244 Rollback should handle system.indexes inserts better
- Closed
-
SERVER-13573 Retry rollback FindCommonPoint before failing (and fasserting)
- Closed
-
SERVER-23392 Increase Replication Rollback (Data) Limit
- Closed
- related to
-
SERVER-18035 Data Replicator: Refactor Rollback Code
- Closed