[SERVER-8574] acquiring distributed lock for upgrade process for 2.2->2.4 has very long timeout. Created: 14/Feb/13 Updated: 11/Jul/16 Resolved: 21/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0-rc2 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Michael O'Brien | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
if the distributed lock to initiate the upgrade process can not be acquired for some reason (e.g. a config server is down) it continues to retry for up to 15 mins before failing completely. |
| Comments |
| Comment by auto [ 21/Feb/13 ] |
|
Author: {u'date': u'2013-02-21T00:28:39Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |