[SERVER-28637] WiredTiger journal files accumulate with each server start/stop Created: 05/Apr/17 Updated: 06/Dec/17 Resolved: 24/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage, WiredTiger |
| Affects Version/s: | 3.4.3 |
| Fix Version/s: | 3.4.10, 3.5.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cory Mintz | Assignee: | Susan LoVerso |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||||||||
| Sprint: | Storage 2017-05-29 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
If I start MongoDB 3.4.3, wait a few seconds, ctrl-c out, and repeat the journal directory adds a new WiredTigerLog.* file for every restart. i.e.
Following the exact same procedure with MongoDB 3.4.2, the old files are cleaned up
|
| Comments |
| Comment by Ramon Fernandez Marina [ 14/Sep/17 ] |
|
Author: {'username': u'bvpvamsikrishna', 'name': u'Susan LoVerso', 'email': u'sue@mongodb.com'}Message: (cherry picked from commit 7d5b12eac722a0f3a564e0c7f778e525f06b6bf7) |
| Comment by Githook User [ 22/May/17 ] |
|
Author: {u'username': u'sueloverso', u'name': u'Susan LoVerso', u'email': u'sue@mongodb.com'}Message: |
| Comment by Susan LoVerso [ 18/May/17 ] |
|
While |
| Comment by Alexander Gorrod [ 02/May/17 ] |
|
The changes to implement this change are going to happen at the WiredTiger level, and the work is covered by |
| Comment by Susan LoVerso [ 05/Apr/17 ] |
|
Yes, we should be able to split out the recovery/archiving so that it archives after a clean shutdown. I have opened |
| Comment by Alexander Gorrod [ 05/Apr/17 ] |
|
cory.mintz I believe what you are seeing is a deliberate consequence of sue.loverso Do you think there is a reasonable path to cleaning up old log files on clean shutdown? I believe that would retain the behavior Cory wants, while still keeping the benefit of |