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

Server replication "hung"

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.0.5
    • Component/s: Replication
    • None
    • Environment:
      Linux 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64
    • Linux

      Recently, after a series of server reboots, one of our server stopped replicating data from primary. Everything in logs looks ok, except that it stalled in the "replset syncing to ..." phase after startup. Restarting either primary or secondary didn't help. I think that the simplest solution would be resyncing from scratch, but the database is large enough and write volume is intensive enough for full replication to take about 16-20 hours that we prefer not to spend right now.
      MMS links follow.
      Secondary in question: https://mms.10gen.com/host/detail/cfa77b8ec3d9ab5870a3a6892c43ba8f
      Its primary: https://mms.10gen.com/host/detail/c070029ad468a0141a72471130b108df

        1. secondary.log.gz
          341 kB
          Aristarkh Zagorodnikov

            randolph@mongodb.com Randolph Tan
            onyxmaster Aristarkh Zagorodnikov
            0 Vote for this issue
            2 Start watching this issue