Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- rollback-optional

Sprint:
Repl 2018-05-07
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

Current rollback limit is 300MB, but it's not practical for high-throughput systems that write 100's of MB per second. We should consider upping the limit or removing it completely.

is duplicated by

SERVER-5929 Expand limit for rollback beyond existing 300mb

Closed

is related to

SERVER-71156 Fatal Assertion 40507 UnrecoverableRollbackError and Mongo Crash with 4.0.27 WT

Closed

related to

SERVER-32358 Rollback can used unbounded memory

Closed

SERVER-5930 rollback loop should be smarter

Closed

SERVER-47918 Improve "replSet too much data to roll back" to include reason for "too much data" limit

Closed

Assignee:: Judah Schvimer
Reporter:: Alexander Komyagin (Inactive)
Participants:: Alexander Komyagin, Daniel Pasette, Eric Milkie, Judah Schvimer, Scott Hernandez, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 13 Start watching this issue

Created:: Mar 29 2016 01:40:51 PM UTC
Updated:: Nov 08 2022 02:50:13 PM UTC
Resolved:: Apr 17 2018 05:26:01 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates