[SERVER-5855] db.eval('db.fsyncLock()') hangs mongod Created: 16/May/12  Updated: 11/Jul/16  Resolved: 16/May/12

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

Type: Bug Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Comments   
Comment by Andy Schwerin [ 10/Jul/12 ]

Test is in fsync.js:

assert( !db.eval('db.fsyncLock()').ok, "eval('db.fsyncLock()') should fail." )

Comment by auto [ 16/May/12 ]

Author:

{u'login': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@10gen.com'}

Message: SERVER-5855 Refuse to run an fsyncLock() command from a locked context.

fsyncLock() inside a locked context deadlocks the server immediately.
Branch: master
https://github.com/mongodb/mongo/commit/e422ec341c86a65348812344f607b3d46d086e75

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