[SERVER-24796] Distlock acquisition must not retry at the level of individual 'findAndModify' command Created: 24/Jun/16  Updated: 19/Jul/16  Resolved: 30/Jun/16

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Kaloian Manassiev
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
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

Currently, the dist lock catalog retries the 'findAndModify' operations on NotMaster errors. In addition, in the dist lock manager there is a retry logic for the same set of errors.

The calls inside the dist lock catalog must be made to not retry because if the previous write succeeded, it would return a status indicating that the lock is busy, when in fact it is actually not. This throws off the outer retry logic.



 Comments   
Comment by Githook User [ 30/Jun/16 ]

Author:

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

Message: SERVER-24796 DistLockCatalog must not retry 'findAndModify' calls
Branch: master
https://github.com/mongodb/mongo/commit/efbd71cabb222df40effda385467d8fd7703775c

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