[SERVER-27935] Fix serialization of concurrent fsyncLock execution Created: 07/Feb/17  Updated: 05/Apr/17  Resolved: 15/Feb/17

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: 3.4.0
Fix Version/s: 3.4.3, 3.5.4

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

Issue Links:
Backports
Depends
is depended on by SERVER-27897 Remove uses of temporary RAII objects Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Storage 2017-03-06
Participants:
Linked BF Score: 0

 Description   

The exclusive lock is only held momentarily, as no variable is named to keep the RAII type around for the duration of the scope.



 Comments   
Comment by Githook User [ 03/Mar/17 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-27935 Fix serialization of concurrent fsyncLock executions

(cherry picked from commit e02c45b789458bb5bb3ba8350f4fd91305933deb)
Branch: v3.4
https://github.com/mongodb/mongo/commit/872db0ea7eaa70a1d323b02343a1872d633196be

Comment by Githook User [ 15/Feb/17 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-27935 Fix serialization of concurrent fsyncLock executions
Branch: master
https://github.com/mongodb/mongo/commit/e02c45b789458bb5bb3ba8350f4fd91305933deb

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