Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 4.1.12
Affects Version/s: 2.6.7
Component/s: Admin
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Storage NYC 2019-05-20
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

Vote for this issue.url
0.2 kB
Apr 11 2018 02:30:09 AM UTC

causes

SERVER-70444 fsync lock/unlock command fails when primary has not fully shutdown

Closed

is duplicated by

SERVER-19263 mongod hangs on db.shutdownServer() if fsyncLock()

Closed

SERVER-3694 Mongod can't be shutdown while it is fsync locked

Closed

is related to

SERVER-70444 fsync lock/unlock command fails when primary has not fully shutdown

Closed

Assignee:: Gregory Wlodarek

Reporter:: Eoin Brazil

Participants:: Eoin Brazil, Eric Milkie, Githook User, Gregory Wlodarek, Ramon Fernandez Marina

Votes:: 3 Vote for this issue

Watchers:: 15 Start watching this issue

Created:: Mar 13 2015 06:57:43 PM UTC

Updated:: Apr 12 2023 06:20:17 PM UTC

Resolved:: May 15 2019 02:06:23 PM UTC

Confidence Status Last Update:: 09/May/19 5:35 PM