[SERVER-33934] Creating an unsharded collection can cause dist lock to time out Created: 16/Mar/18  Updated: 29/Oct/23  Resolved: 23/May/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.3
Fix Version/s: 4.0.0-rc1, 4.1.1

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-33639 Concurrent writes against non-existen... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Sharding 2018-05-21, Sharding 2018-06-04
Participants:
Linked BF Score: 17

 Description   

when enough threads try to do it on the same database at the same time.

This is because all of them will try to grab the dist lock on the database. The dist lock algorithm doesn't have fair scheduling so it is possible for a single thread to be starved by other threads if there is enough contention on it.



 Comments   
Comment by Githook User [ 23/May/18 ]

Author:

{'username': 'jannaerin', 'name': 'jannaerin', 'email': 'golden.janna@gmail.com'}

Message: SERVER-33934 Protect against distlock acquisition timeout at createCollection time

(cherry picked from commit e382ac37427c519e5d39b909f96b45c2a32d072a)
Branch: v4.0
https://github.com/mongodb/mongo/commit/ae6e0d7954a45d48634598d1fe8282c4452be861

Comment by Githook User [ 23/May/18 ]

Author:

{'username': 'jannaerin', 'name': 'jannaerin', 'email': 'golden.janna@gmail.com'}

Message: SERVER-33934 Protect against distlock acquisition timeout at createCollection time
Branch: master
https://github.com/mongodb/mongo/commit/e382ac37427c519e5d39b909f96b45c2a32d072a

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