[SERVER-9610] Can't start a new sharded cluster on 2.4.3 - Waiting for distributed lock config Created: 07/May/13 Updated: 10/Dec/14 Resolved: 09/Sep/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Patrick Roy | Assignee: | David Hows |
| Resolution: | Done | Votes: | 1 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
EC2 Amazon Linux AMI release 2013.03 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
I'm trying to setup a sharded cluster with 2 replica sets and the config servers were empty, I started them and tried mongos. This is the log: mongos --configdb mongodb-ec2-100:27019,mongodb-ec2-105:27019,mongodb-ec2-110:27019 Tue May 7 20:27:23.046 [mongosMain] MongoS version 2.4.3 starting: pid=32156 port=27017 64-bit host=ip-10-158-33-56 (--help for usage) Tue May 7 20:27:23.086 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-100:27019] |
| Comments |
| Comment by David Hows [ 26/Aug/13 ] |
|
Hi Patrick, Just following up. Have you been able to upgrade to 2.4 subsequently? Is this still an ongoing issue for you? Regards, |
| Comment by Patrick Roy [ 15/May/13 ] |
|
No I started with 2.4 and got that message. The actual process was:
I actually downgraded again to 2.2.4 and it's working fine |
| Comment by Eliot Horowitz (Inactive) [ 15/May/13 ] |
|
You would get that if you had a mongos started with 2.2, then had a failed upgrade with 2.4, then tried 2.4 again. Is that possible? |