[SERVER-41267] size of Journal files are increasing not getting cleaned up Created: 22/May/19  Updated: 15/Nov/21  Resolved: 16/Jun/19

Status: Closed
Project: Core Server
Component/s: Diagnostics, Storage, WiredTiger
Affects Version/s: 3.4.1
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Yogesh Jadhav Assignee: Dmitry Agranat
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to WT-3985 Pre-allocated log files accumulate on... Closed
Participants:

 Description   

Using mongodb version 3.4.1.

Size of journal file are not getting cleaned up after upgrade patch of windows where mongodb is running. Nothing is showing in logs.

Journal files are increasing rapidly though do not having the Space in data directory can we delete the journal files. 



 Comments   
Comment by Dmitry Agranat [ 29/May/19 ]

Hi yogeshtj889,

Based on the data you've uploaded, I was not able to find any evidence of the issue you've reported. However, I also see a gap of 12 days between May 7th and May 19th, which might explain this.

We had some improvements in this area, specifically WT-3904, which was fixed in 3.4.14 and WT-3985 which was fixed in 3.6.4. I recommend upgrading your cluster to the latest MongoDB version 3.6.12. If you experience this issue again after the suggested upgrade, please file a new report and we'll be happy to help.

Thank you,
Dima

Comment by Yogesh Jadhav [ 24/May/19 ]

I want to tell you that while window patch upgradation mongodb service not taken down means it was unclean shutdown. after that we observe Journal files start to increase then we deleted some of them and cleared the space. we took restart of mongodb server after restart journal file reduced to 0 KB though also it is again start to increase.

we have uploaded in Secure Uploader "diagnostic.data" and "logs" from second time restart of mongodb server, we are unable to provide you logs from window OS restart due its size.

Thanks
Yogesh

Comment by Yogesh Jadhav [ 23/May/19 ]

Hi Daniel, 

 

We are using WiredTiger storage engine. I will upload "diagnostic.data" and Logs soon.

Comment by Danny Hatcher (Inactive) [ 23/May/19 ]

Are you using MMAPv1 or WiredTiger as your storage engine?

Please upload the mongod logs and the contents of the "diagnostic.data" folder (located under your $dbpath) to our Secure Uploader covering the timeframe since your Windows upgrade until now. Please note that only MongoDB engineers will be able to see data uploaded there and it will be automatically deleted after 90 days.

Generated at Thu Feb 08 04:57:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.