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

Can't initiate a ReplSet with chainingAllowed: False

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.8.0-rc1
    • Component/s: Replication
    • Labels:
    • ALL

      Problem

      Starting a ReplSet with chainingAllowed: false appears to hang. Nothing in the log

      2014-11-22T01:29:45.868-0500 I CONTROL  [initandlisten] MongoDB starting : pid=24593 port=27017 dbpath=/data2/db/db100 64-bit host=ip-10-93-7-23.ec2.internal
      2014-11-22T01:29:45.868-0500 I CONTROL  [initandlisten] db version v2.8.0-rc1
      2014-11-22T01:29:45.868-0500 I CONTROL  [initandlisten] git version: 0a02891e3f155e5a187ee14c774d42cbdb290652
      2014-11-22T01:29:45.868-0500 I CONTROL  [initandlisten] build info: Linux build19.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
      2014-11-22T01:29:45.868-0500 I CONTROL  [initandlisten] allocator: tcmalloc
      2014-11-22T01:29:45.868-0500 I CONTROL  [initandlisten] options: { net: { port: 27017 }, processManagement: { fork: true }, replication: { oplogSizeMB: 500, replSet: "mp" }, storage: { dbP
      ath: "/data2/db/db100", engine: "mmapv1", mmapv1: { syncPeriodSecs: 14400.0 } }, systemLog: { destination: "file", path: "/data3/db/db100/server.log" } }
      2014-11-22T01:29:45.878-0500 I JOURNAL  [initandlisten] journal dir=/data2/db/db100/journal
      2014-11-22T01:29:45.879-0500 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
      2014-11-22T01:29:45.927-0500 I INDEX    [initandlisten] allocating new ns file /data2/db/db100/local.ns, filling with zeroes...
      2014-11-22T01:29:45.984-0500 I STORAGE  [FileAllocator] allocating new datafile /data2/db/db100/local.0, filling with zeroes...
      2014-11-22T01:29:45.984-0500 I STORAGE  [FileAllocator] creating directory /data2/db/db100/_tmp
      2014-11-22T01:29:46.222-0500 I STORAGE  [FileAllocator] done allocating datafile /data2/db/db100/local.0, size: 64MB,  took 0.236 secs
      2014-11-22T01:29:46.225-0500 I REPL     [initandlisten] Did not find local replica set configuration document at startup;  NoMatchingDocument Did not find replica set configuration documen
      t in local.system.replset
      2014-11-22T01:29:46.226-0500 I NETWORK  [initandlisten] waiting for connections on port 27017
      2014-11-22T01:30:26.520-0500 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:51467 #1 (1 connection now open)
      2014-11-22T01:30:26.523-0500 I NETWORK  [conn1] end connection 127.0.0.1:51467 (0 connections now open)
      2014-11-22T01:30:26.525-0500 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:51468 #2 (1 connection now open)
      2014-11-22T01:30:26.527-0500 I NETWORK  [conn2] end connection 127.0.0.1:51468 (0 connections now open)
      2014-11-22T01:30:26.813-0500 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:51471 #3 (1 connection now open)
      2014-11-22T01:30:27.259-0500 I NETWORK  [conn3] end connection 127.0.0.1:51471 (0 connections now open)
      2014-11-22T01:30:36.081-0500 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:51473 #4 (1 connection now open)
      2014-11-22T01:31:58.591-0500 I REPL     [conn4] replSetInitiate admin command received from client
      

      Reproduce

      /home/ec2-user/mongodb-linux-x86_64-2.8.0-rc1/bin/mongod --port 27017 --dbpath /data2/db/db100 --logpath /data3/db/db100/server.log --fork --storageEngine=mmapv1 --syncdelay 14400 --replSet mp --oplogSize 500
      /home/ec2-user/mongodb-linux-x86_64-2.8.0-rc1/bin/mongod --port 27018 --dbpath /data2/db/db200 --logpath /data3/db/db200/server.log --fork --storageEngine=mmapv1 --syncdelay 14400 --replSet mp --oplogSize 500
      /home/ec2-user/mongodb-linux-x86_64-2.8.0-rc1/bin/mongod --port 27019 --dbpath /data2/db/db300 --logpath /data3/db/db300/server.log --fork --storageEngine=mmapv1 --syncdelay 14400 --replSet mp --oplogSize 500
      
      var config = { _id: "mp", members: [ { _id: 0, host: "localhost:27017",priority:10 }, {_id: 1, host: "localhost:27018" }, { _id: 3, host: "localhost:27019" } ],settings: {chainingAllowed: false} }; 
      rs.initiate( config ); 
      

      Workaround

      With chainingAllowed: true, the ReplSet will start up just fine.

            Assignee:
            Unassigned Unassigned
            Reporter:
            alvin Alvin Richards (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: