[SERVER-24085] LockManager doesn't grant all read requests on GlobalLock MODE_S grant Created: 06/May/16  Updated: 02/Feb/17  Resolved: 16/Jun/16

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: None
Fix Version/s: 3.2.13, 3.3.9

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.2
Sprint: Integrate+Tuning 16 (06/24/16)
Participants:
Linked BF Score: 0

 Description   

When granting the global lock in MODE_S, the locking policy switches to compatibleFirst, allowing readers to skip queued writers. However, existing readers that are waiting behind writers on the global lock are not released.

This may result in existing readers becoming blocked when running the fsyncLock command.



 Comments   
Comment by Githook User [ 02/Feb/17 ]

Author:

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

Message: SERVER-24085: Grant existing lock requests on enabling compatibleFirst

(cherry picked from commit 5bbf5083162d1982f579dcfaea254c32aa30805b)
Branch: v3.2
https://github.com/mongodb/mongo/commit/77e9cf34ead0adb05a66f98b7e1541a95805495d

Comment by Githook User [ 16/Jun/16 ]

Author:

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

Message: SERVER-24085: Grant existing lock requests on enabling compatibleFirst
Branch: master
https://github.com/mongodb/mongo/commit/5bbf5083162d1982f579dcfaea254c32aa30805b

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