[SERVER-2789] requesting unlock after fsync-lock should block until actually unlocked Created: 17/Mar/11  Updated: 12/Jul/16  Resolved: 04/Apr/11

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

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Participants:

 Description   

Currently just returns an "unlock requested" message immediately.



 Comments   
Comment by Mathias Stearn [ 04/Apr/11 ]

http://www.mongodb.org/display/DOCS/fsync+Command#fsyncCommand-Changesin1.9

Comment by Mathias Stearn [ 18/Mar/11 ]

eng work completed. leaving open to make sure I update the wiki.

Comment by auto [ 18/Mar/11 ]

Author:

{u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: db.fsyncUnlock() now waits for unlock to actually happen SERVER-2789
https://github.com/mongodb/mongo/commit/1f0b0fe089e31e159344a9472513c31d5c577318

Comment by auto [ 18/Mar/11 ]

Author:

{u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: Add shell helpers db.fsyncLock() and db.fsyncUnlock() and clean up messages SERVER-2789
https://github.com/mongodb/mongo/commit/2775fa3e2b8a4a29abf9cc2480aa08033e491856

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