[SERVER-20653] Make default distributed lock timeout for dropCollection 2 seconds Created: 25/Sep/15  Updated: 07/Oct/15  Resolved: 01/Oct/15

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding A (10/09/15)
Participants:
Linked BF Score: 0

 Description   

In general in a sharded system, it is preferable for the dropCollection command not to return immediately with a lock timeout error if the lock happens to be busy at the exact moment the command is issued.

Allow the dropCollection command to wait up to 2 seconds before returning a LockBusy error.



 Comments   
Comment by Githook User [ 29/Sep/15 ]

Author:

{u'username': u'EshaMaharishi', u'name': u'Esha Maharishi', u'email': u'esha.maharishi@10gen.com'}

Message: SERVER-20653 make default distributed lock timeout for dropCollection 2 seconds
Branch: master
https://github.com/mongodb/mongo/commit/1f34fa3204a4212ee724c330331bdef7ad3a4c44

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