Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- datarepl3.2

Assigned Teams:

Replication
Case:
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Azat Khuzhin
Participants:: [DO NOT USE] Backlog - Replication Team, Azat Khuzhin, Eric Milkie, Scott Hernandez
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: May 25 2012 08:05:16 AM UTC
Updated:: Dec 06 2022 05:33:02 AM UTC
Resolved:: May 02 2018 07:16:23 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates