[SERVER-33187] Journal data are not cleared by WiredTiger Created: 08/Feb/18 Updated: 06/Dec/22 Resolved: 09/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sandeep [X] | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | Bug, Cleanup | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoServer:3.4 version |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Hi Team, Thanks for your continuous support !! Reference links It has mentioned that Above statement implies that journal folder will keep on growing and never gets cleared ,
Thanks & Regards |
| Comments |
| Comment by Eric Milkie [ 09/Feb/18 ] | ||
|
Please follow the linked WT ticket for updates. | ||
| Comment by Sandeep [X] [ 09/Feb/18 ] | ||
|
Dear Team, I've attached file list of journal directory journal_dir_listfiles.txt Thanks & Regards | ||
| Comment by Susan LoVerso [ 08/Feb/18 ] | ||
|
I opened | ||
| Comment by Susan LoVerso [ 08/Feb/18 ] | ||
|
There are no known issues that I'm aware of (at least looking back on changes/fixes to relevant files). Archiving log files no longer needed is determined by checkpoints. Looking at FTDC checkpoints are happening regularly and nothing looks out of the ordinary there. bruce.lucas's analysis provides a clue. Looking at the mongod logs, the log server thread that is responsible for both pre-allocating log files and archiving old ones got an error and exited:
Therefore once that happened and the thread exited with an error, it never archived nor pre-allocated log files. I'll open a ticket to consider whether that should be a fatal error, but in 3.4.0 it is and the only way to restart that internal thread is a restart. | ||
| Comment by Susan LoVerso [ 08/Feb/18 ] | ||
|
Can you attach an ls -l of the journal directory please? | ||
| Comment by Bruce Lucas (Inactive) [ 08/Feb/18 ] | ||
|
It looks like up until about A we are recycling old log files, but at A we stop doing that and so starting at B we are having to create new log files. This condition persists throughout the rest of the FTDC data, and as expected the number of "pre-allocated log files not ready" matches the number of existing log files. There are one or two other things that change at about the same time, relevance TBD. sue.loverso does this match any known issued in 3.4.0? | ||
| Comment by Sandeep [X] [ 08/Feb/18 ] | ||
|
Sorry Team, | ||
| Comment by Sandeep [X] [ 08/Feb/18 ] | ||
|
Dear Team,
Thanks & Regards | ||
| Comment by Sandeep [X] [ 08/Feb/18 ] | ||
|
diagnostic.data.rar Also i have attached the* "$dbpath/diagnostic.data* for your analysis Thanks & awaiting for your reply Thanks & Regards |