[SERVER-15269] Reenable killall.js after implementing priorities for the shutdown X-lock thread Created: 16/Sep/14  Updated: 02/Aug/18  Resolved: 21/Nov/14

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 2.8.0-rc1

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Participants:

 Description   

The jstests/disk/killall.js unit-test is being disabled, because currently we do not have priorities in the lock manager and the shutdown thread queues behind other operations.



 Comments   
Comment by Githook User [ 21/Nov/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-15269 db.shutdownServer terminates JS execution cleanly
Branch: master
https://github.com/mongodb/mongo/commit/f56ea73672e1eebde4d2e9cef2f8fca0d84f0956

Comment by Githook User [ 12/Nov/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-15269 Make Global and Flush lock requests jump the queue

The S and X modes on the Global and Flush locks are used for servicing
functions such as shutdown or replication step-down. Those should be
blocked minimally, so they should be able to get the lock with preference.
Branch: master
https://github.com/mongodb/mongo/commit/df09ff06181a690bc504356a8a82c71163022127

Comment by Githook User [ 12/Nov/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-15269 Move Lock manager queue management to a separate class
Branch: master
https://github.com/mongodb/mongo/commit/d6184ee7b6a365852adeb7d2ad084f288418f717

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