[SERVER-16010] monogs waited XXs for distributed lock configUpgrade for upgrading config database to new format v5 Created: 07/Nov/14 Updated: 04/Dec/14 Resolved: 04/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierre Lemordant | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | follow documentation "deploy a sharded cluster" : http://docs.mongodb.org/manual/tutorial/deploy-shard-cluster/ |
| Participants: |
| Description |
|
I'm currently trying to deploy a "mongod 2.6.5" sharded cluster on centOS 7 VMs where firewalls are disabled and time synchronized with ntp. Starting config serversOn 3 VM, I run the following command (as indicated in the doc)
They started correctly and I can observe following output logs
Starting mongos instanceOn another VM, I run the following command
Of course the provided IP are the (previously started) config server ones. I can observe the mongos could establish the connection to the config server as shown below
But as you can see the log says that the mongos is waiting "for distributed lock configUpgrade ..." until it reaches 1200s and stops. These are the logs from a config server (there are similar logs for each config server) when i start the mongos instance,
As I followed each step of the doc [1], please could you tell me what I missed here ? [1] http://docs.mongodb.org/manual/tutorial/deploy-shard-cluster/ |
| Comments |
| Comment by Ramon Fernandez Marina [ 04/Dec/14 ] |
|
Hi pierre.lemordant_mongodb@fastconnect.fr, thanks for letting us know. Glad to hear your cluster is up and running. |
| Comment by FastConnect Team [ 04/Dec/14 ] |
|
Hi Ramon, Thank you for your response. Regards, Pierre |
| Comment by Ramon Fernandez Marina [ 03/Dec/14 ] |
|
pierre.lemordant_mongodb@fastconnect.fr, apologies for the late reply. The only time I've seen the "waited XXs for distributed lock configUpgrade for upgrading config database to new format v5" message is when the clocks on the config servers were too far apart. You do mention using ntp, so I'd like to rule out a possible glitch or misconfiguration (or an issue with the virtualization software). Can you please check the date on all three config servers? If they're in sync, can you please post the full logs of all three config servers? |