[SERVER-20726] Improve mongod behavior after failed msync() call Created: 01/Oct/15 Updated: 06/Dec/22 Resolved: 14/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1, Storage |
| Affects Version/s: | 3.0.5, 3.0.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jeremy Sternad [X] | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | Bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 14.04, 2 GB RAM, 50 GB Disk Space
|
||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
The requested improvement is to either not shut down or improve the error message. Original descriptionthe mongod service sometimes crashes with the following log:
This happens always after an uptime for about 3 to 4 days. I was searching the internet for a solution, but didn't find one. I found an older issue which is similiar to the above error message. |
| Comments |
| Comment by Ramon Fernandez Marina [ 18/Apr/16 ] | ||||||||||||||||||||||||||
|
Repurposing this as an improvement request as per Mark's last comment. | ||||||||||||||||||||||||||
| Comment by Mark Callaghan [ 16/Apr/16 ] | ||||||||||||||||||||||||||
|
Please reopen this as a feature request. The requested improvement is to either not shut down or improve the error message. In MySQL, we encounter disk full for the binlog and InnoDB. They go into loops with: sleep, retry, print message to error log, repeat and this allows a DBA to correct the problem. But you might not be investing in mmap at this point. The easier solution is to print something indicating that the disk is full. It is hard to notice that from the error message below. LevelDB had similar fun with mmap:
| ||||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 01/Oct/15 ] | ||||||||||||||||||||||||||
|
Jayrizon, as per these messages in the log:
mongod was not able to successfully complete a msync(2) call and shut itself down to safeguard your data. This error is triggered by a problem in the storage layer, so please search your system logs for further information on what's causing this issue. It could be a problem in the virtualization layer as well. This behavior is not a bug in the server, so I'm going to close this ticket. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. Regards, |