[SERVER-17589] Allow mongod shutdown whilst fsync locked Created: 13/Mar/15  Updated: 12/Apr/23  Resolved: 15/May/19

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 2.6.7
Fix Version/s: 4.1.12

Type: Improvement Priority: Major - P3
Reporter: Eoin Brazil Assignee: Gregory Wlodarek
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File Vote for this issue.url    
Issue Links:
Duplicate
is duplicated by SERVER-19263 mongod hangs on db.shutdownServer() i... Closed
is duplicated by SERVER-3694 Mongod can't be shutdown while it is ... Closed
Problem/Incident
causes SERVER-70444 fsync lock/unlock command fails when ... Closed
Related
related to DOCS-5469 fsyncLock() prevents the mongod proce... Closed
is related to SERVER-70444 fsync lock/unlock command fails when ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-05-20
Participants:

 Description   

Hi,

It appears that the mongod is unable to shutdown when a shutdown command is issued while it has been fsync locked.

A hard kill is necessary to shutdown the mongod in this instance.

Thanks!
Eoin



 Comments   
Comment by Githook User [ 15/May/19 ]

Author:

{'email': 'gregory.wlodarek@mongodb.com', 'name': 'Gregory Wlodarek', 'username': 'GWlodarek'}

Message: SERVER-17589 Allow mongod to shutdown while fsync locked
Branch: master
https://github.com/mongodb/mongo/commit/76f1710d8230553d4f458f175e79dedbbf3e092c

Comment by Eric Milkie [ 26/Apr/19 ]

The current behavior here is that shutdown hangs when the server is fsync-locked, and there is no way to recover from this gracefully since the server has already closed all sockets.

Comment by Ramon Fernandez Marina [ 02/Jul/15 ]

I'm changing this into an improvement request and sending it for triaging.

Generated at Thu Feb 08 03:44:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.