[SERVER-80716] Problem with growing WiredTigerHS.wt file Created: 01/Sep/23 Updated: 27/Oct/23 Resolved: 05/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrzej Nowak | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Good morning. In the past week, we experienced an issue with MongoDB 6.0.5 - it's a replica set consisting of 4 data nodes, each two in different data centers and an arbiter in the cloud. Due to an application error, the WiredTigerHS.wt file grew significantly within a few minutes, filling up the filesystem on 3 of the data nodes, which resulted in a database outage. Since we are currently in the process of migrating a large number of databases from MongoDB 3.6 to MongoDB 6, we would like to find a way to prevent such a situation from happening again. Is there a possibility to move this file to a different filesystem or any other option to prevent a similar situation in the future? |
| Comments |
| Comment by Edwin Zhou [ 05/Sep/23 ] |
|
The history store was introduced in 4.4 and the default parameter "minSnapshotHistoryWindowInSeconds" was increased by To further investigate this issue, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project. Since this behavior appears to be working as designed, I will now close this ticket. Kind regards, |
| Comment by Alexander Gorrod [ 04/Sep/23 ] |
|
Thanks for using MongoDB, and I'm sorry you are having some operational issues when upgrading MongoDB. This Jira project is for standalone WiredTiger users - I'm moving the ticket to a more appropriate Jira project for triage. |