[SERVER-35931] Mongod killed when database disk is full (with directoryPerDB: true) Created: 02/Jul/18  Updated: 02/Jul/18  Resolved: 02/Jul/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.20, 3.4.15, 3.6.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Martin Polák Assignee: Nick Brewer
Resolution: Duplicate Votes: 0
Labels: storage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-35930 Mongod killed when database disk is f... Closed
Participants:

 Description   

I'm using MongoDB 3.6.5 (already tested on 3.2 / 3.4) and i have enabled "directoryPerDB" in /etc/mongo.conf.

#mongod.conf

storage:
dbPath: /var/lib/mongodb
journal:
enabled: true
directoryPerDB: true

I created LVM disk's for my databases and symlinked in to /var/lib/mongodb

Here is problem:

When one of these lvm's is full, it will kill mongod service, so i can't use the rest of databases, where is free space on storage. Because of that, this will kill my primary node and subsequently the secondary node.

This is critical problem for us.

Your help will be greatly appreciated!


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