[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: |
|
||||||||
| 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: |
| Comment by Alexander Komyagin [ 09/Jun/14 ] |
|
I suspect that we just catch the exception in mongosMain thread. |