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

Slave hits Fatal Assertion 16361 during initial sync: objects in a capped ns cannot grow

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.4.4
    • Component/s: Replication
    • Labels:
      None
    • Environment:
      centos6
    • Linux
    • Hide

      Startup a clean mongo setup for replica set
      Wait - see crash.

      Show
      Startup a clean mongo setup for replica set Wait - see crash.

      Slave crashes during init sync - after 24+ hours

      Primary:

      sprawk:PRIMARY> db.getReplicationInfo();
      {
      	"logSizeMB" : 28610.2294921875,
      	"usedMB" : 537.86,
      	"timeDiff" : 89633,
      	"timeDiffHours" : 24.9,
      	"tFirst" : "Sat Jun 22 2013 15:22:26 GMT+0200 (CEST)",
      	"tLast" : "Sun Jun 23 2013 16:16:19 GMT+0200 (CEST)",
      	"now" : "Sun Jun 23 2013 16:16:19 GMT+0200 (CEST
      

      Servers are max 2 seconds out of sync....

      Config on server:
      master=true
      replSet=sprawk
      keyFile = /var/lib/mongo/sprawk.key
      oplogSize = 28610

      Config on slave:
      replSet=sprawk
      keyFile = /var/lib/mongo/sprawk.key

      I will now try again with the same oplogSize specified on the slave...

        1. mongo-crash.txt
          20 kB
        2. mongo-crash2.log
          12 kB
        3. mongod.log.gz
          1.72 MB

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            niccottrell Nic Cottrell (Personal)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: