[SERVER-33663] Create setParameter to control creation of rollback data files Created: 05/Mar/18 Updated: 29/Oct/23 Resolved: 07/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Kyle Suarez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | rollback-non-functional | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Repl 2018-03-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
During rollback, replication writes out data files that contain documents that will be deleted after rollback completes. This means that the time it takes to execute a rollback scales linearly with the amount of data that has been inserted after the common point. There may be cases when a user might not care about these deleted documents and simply want rollback to execute as fast as possible. We can add a startup-only setParameter that controls whether or not these rollback data files will be created or not; the default behavior will be to always write out data files. |
| Comments |
| Comment by Githook User [ 07/Mar/18 ] |
|
Author: {'email': 'kyle.suarez@mongodb.com', 'name': 'Kyle Suarez', 'username': 'ksuarz'}Message: Users can suppress the creation of rollback data files by setting the |