[SERVER-69716] Mongo DB crashing with an error: Not enough storage is available to process this command Created: 15/Sep/22  Updated: 27/Sep/22  Resolved: 27/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.2.6
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mamatha K Assignee: Yuan Fang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mongodb_LP (2).log     Text File mongodb_LP_2022-08-22T20-46-44.log    
Issue Links:
Duplicate
duplicates SERVER-69717 Mongo DB crashing with an error: Not ... Closed
duplicates WT-9868 Mongo DB crashing with an error: Not ... Closed
Operating System: ALL
Participants:

 Description   

Mongo DB is crashing which is causing the application to fail. When extracted mongo Db logs found below error.

 

2022-09-11T00:36:21.977+0000 E STORAGE [WTJournalFlusher] WiredTiger (-28992) [1662856581:400819][7072:1995194080], WT_SESSION.log_flush: journal/WiredTigerLog.0000158373 handle-sync: FlushFileBuffers error: Not enough storage is available to process this command.

2022-09-11T00:36:21.989+0000 I - [WTJournalFlusher] Invariant failure: s->log_flush(s, “sync=on”) resulted in status UnknownError: -28992: Not enough storage is available to process this command.

After restarting application servers mongo started working as expected. But this is the second occurrence, and we wanted to know the resolution to avoid future occurrences. 

Note : There's enough space available in disks.

800gb in D drive, 40-50gb is C drive. And mongo DB is around 720gb.

Mongo DB version used : 3.2.6.

Operating system : windows

Attaching full logs below from both the occurrences mongodb_LP (2).log.mongodb_LP_2022-08-22T20-46-44.log



 Comments   
Comment by Yuan Fang [ 27/Sep/22 ]

Hi k.mamatha23@gmail.com,

Thank you for your report. Please note that MongoDB 3.2 reached the end of life in Sep 2018 and is no longer supported. I would suggest you upgrade to MongoDB v4.2+.

Based on the log you provided, this does not appear to be a SERVER bug. It looks like this thread on MongoDB Developer Community Forums discusses this. Can you see if it helps? 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.

Regards,

Yuan

Generated at Thu Feb 08 06:14:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.