[DOCS-11631] Replication rollback on WiredTiger does not have data limit Created: 17/Apr/18 Updated: 30/Oct/23 Due: 04/May/18 Resolved: 09/May/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | docs-grab-0504 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 40 weeks ago | ||||||||
| Epic Link: | DOCS: 4.0 Server | ||||||||
| Description |
|
The new replication rollback algorithm for WiredTiger in MongoDB 4.0 has no limit on the amount of data that can be rolled back, unlike the old algorithm which had a 300MB limit. This limit is described here: https://docs.mongodb.com/manual/core/replica-set-rollbacks/#rollback-limitations. Scope
Impact to other docs outside of this productnone (per marian search, mentions of rollback link back to the manual page) |
| Comments |
| Comment by Githook User [ 09/May/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |