[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: File upgrade_cluster_v3_to_v4_config_down.js    
Issue Links:
Related
is related to DOCS-1145 add section on forcing dist locks to ... Closed
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.
for upgrade process we might want to make this fail more quickly so that it is clearer to the user what is happening, otherwise it is a bit concerning to see an upgrade process spam the logs with lots of lock acquisition failure messages.



 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: SERVER-8574 contact all config servers before waiting for distributed lock on config upgrade
Branch: master
https://github.com/mongodb/mongo/commit/46436d5fd83099aec712ba513a3a8677924939ed

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