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

replica member never syncs up and starts from scratch multiple times.

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 1.9.0
    • Affects Version/s: 1.7.5
    • Component/s: None
    • None
    • Environment:
      ubuntu,
      mongodb 1.7.5,
      two replica members + 1 arbiter
      java driver connecting to log11 and log12
    • ALL

      seems like the member is not able to initialize fully and tries to start from scratch during the initial sync process.
      the oplog seems to be enough to do the process as it takes about 12h to copydata and create indexes on the new member and the oplog has 51h

      log0x:PRIMARY> db.printReplicationInfo()
      configured oplog size: 79892.4875MB
      log length start to end: 184394secs (51.22hrs)
      oplog first event time: Wed Mar 02 2011 06:38:52 GMT-0800 (PST)
      oplog last event time: Fri Mar 04 2011 09:52:06 GMT-0800 (PST)
      now: Fri Mar 04 2011 09:52:06 GMT-0800 (PST)

      Attached is the log from the log12 the member trying to sync up.

        1. mongod.log.log12.failedtosync.gz
          135 kB
        2. mongod.node1.log.afterRepairDatabase.gz
          263 kB
        3. mongod.finallysynched.gz
          530 kB

            Assignee:
            kristina Kristina Chodorow (Inactive)
            Reporter:
            rgiudici Reinaldo Giudici
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: