-
Type: Task
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
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?