Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-9610

Can't start a new sharded cluster on 2.4.3 - Waiting for distributed lock config

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.3
    • Sharding
    • EC2 Amazon Linux AMI release 2013.03
    • Linux

    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.046 [mongosMain] git version: fe1743177a5ea03e91e0052fb5e2cb2945f6d95f
      Tue May 7 20:27:23.046 [mongosMain] build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49
      Tue May 7 20:27:23.046 [mongosMain] options:

      { configdb: "mongodb-ec2-100:27019,mongodb-ec2-105:27019,mongodb-ec2-110:27019" }

      Tue May 7 20:27:23.086 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-100:27019]
      Tue May 7 20:27:23.087 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-105:27019]
      Tue May 7 20:27:23.088 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-110:27019]
      Tue May 7 20:27:23.116 [mongosMain] scoped connection to mongodb-ec2-100:27019,mongodb-ec2-105:27019,mongodb-ec2-110:27019 not being returned to the pool
      Tue May 7 20:27:23.117 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-100:27019]
      Tue May 7 20:27:23.118 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-105:27019]
      Tue May 7 20:27:23.118 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-110:27019]
      Tue May 7 20:27:23.123 [LockPinger] creating distributed lock ping thread for mongodb-ec2-100:27019,mongodb-ec2-105:27019,mongodb-ec2-110:27019 and process ip-10-158-33-56:27017:1367958443:1804289383 (sleeping for 30000ms)
      Tue May 7 20:27:23.123 [LockPinger] SyncClusterConnection connecting to [mongodb-ec2-100:27019]
      Tue May 7 20:27:23.124 [LockPinger] SyncClusterConnection connecting to [mongodb-ec2-105:27019]
      Tue May 7 20:27:23.124 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-100:27019]
      Tue May 7 20:27:23.125 [LockPinger] SyncClusterConnection connecting to [mongodb-ec2-110:27019]
      Tue May 7 20:27:23.125 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-105:27019]
      Tue May 7 20:27:23.126 [mongosMain] SyncClusterConnection connecting to [mongodb-ec2-110:27019]
      Tue May 7 20:27:34.159 [mongosMain] waited 11s for distributed lock configUpgrade for upgrading config database to new format v4
      Tue May 7 20:27:45.190 [mongosMain] waited 22s for distributed lock configUpgrade for upgrading config database to new format v4
      Tue May 7 20:27:56.221 [mongosMain] waited 33s for distributed lock configUpgrade for upgrading config database to new format v4

      Attachments

        Activity

          People

            david.hows David Hows
            patroy Patrick Roy
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: