[SERVER-519] fsync lock + write op locks up db, preventing subsequent unlock Created: 04/Jan/10  Updated: 12/Jul/16  Resolved: 04/Jan/10

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

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Dwight Merriman
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Discovered while running basic js tests in parallel.

Please see jstests/fsync2.js

Spent a few minutes investigating, can continue if you want but you prob know this code better.



 Comments   
Comment by auto [ 04/Jan/10 ]

Author:

{'name': 'Dwight', 'email': 'dmerriman@gmail.com'}

Message: SERVER-519
changed how we unlock - greediness of writers was a problem
http://github.com/mongodb/mongo/commit/755804209e4dcb17beb0895305310289504296ad

Comment by Aaron Staple [ 04/Jan/10 ]

Sounds like Dwight is going to do it.

Comment by auto [ 04/Jan/10 ]

Author:

{'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-519 adding test
http://github.com/mongodb/mongo/commit/f0d60f2396aa57210aaddf5b208d0d4ab047aded

Generated at Thu Feb 08 02:54:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.