[SERVER-64814] Mongod hangs on shutdown and RAM usage reaches upto 98% Created: 23/Mar/22  Updated: 21/Mar/23  Resolved: 06/Apr/22

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

Type: Bug Priority: Major - P3
Reporter: Ishrat Jahan Assignee: Dmitry Agranat
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-64981 Mongod hangs on shutdown and RAM usag... Closed
Operating System: ALL
Participants:

 Description   

On trying to stop the mongod process using the command - sudo systemctl stop mongod, the process got stuck. And the RAM usage started increasing and reached upto 98%. After the systemd timeout, mongod process was killed.  We saw below log for this

State 'stop-sigterm' timed out. Killing.

In the logs, we also saw, mongod was trying to close connections but it got stuck there as well.

This issue happened on all instances of the replicaset. We tried increasing the systemd timeout to upto 15 min, still the sudo systemctl stop mongod was stuck for 15 mins

After the mongod process was killed, we started it again. It started successfully



 Comments   
Comment by Dmitry Agranat [ 31/Mar/22 ]

Hi ishrat.jahan@gojek.com, the SERVER project is for the supported MongoDB versions while the reported version is on 3.6. If you are able to reproduce this issue on a supported MongoDB version, we'll be happy to take a look. Please preserve the full mongod log and diagnostic.data directory during this reproduction and we'll send you a secure uploader link for this data.

Regards,
Dima

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