[SERVER-13254] journaling code needs some cleanups and misc fixes Created: 18/Mar/14 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1 |
| Affects Version/s: | 2.4.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Dwight Merriman | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
1) look for places in code where the dur::writing() call is implicit as it was done by earlier code and thus not clear – and also not the right contract for writing technically. e.g. in renameCollection() 2) fix groupCommitWithLimitedLocks() to not be used with DurParanoid, as it doesn't support it 3) check that at least one buildbot runs with DurParanoid option for validation (--durOptions 8 iirc) 4) the remapprivateviews rotation through the files is too dumb about files that haven't changed in terms of balancing its work evenly |