[SERVER-14215] Log error when ScopedDistributedLock::acquire fails to acquire the lock before timeout Created: 09/Jun/14  Updated: 25/Oct/14  Resolved: 02/Oct/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.6.1
Fix Version/s: 2.7.8

Type: Bug Priority: Major - P3
Reporter: Alexander Komyagin Assignee: Randolph Tan
Resolution: Done Votes: 1
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Tested
Operating System: ALL
Participants:

 Description   

In the distributed lock code we fail to acquire it if the clock skew on config servers is too high. However, the exception thrown is not visible at least on the 2.6 upgrade path.



 Comments   
Comment by Githook User [ 02/Oct/14 ]

Author:

{u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-14215 Log error when ScopedDistributedLock::acquire fails to acquire lock before timeout
Branch: master
https://github.com/mongodb/mongo/commit/cfddfb4b976a38a23f319abae6021c5864fa16d9

Comment by Alexander Komyagin [ 09/Jun/14 ]

I suspect that we just catch the exception in mongosMain thread.

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