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

On restart, sync source not set until first write

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.0-rc3
    • Component/s: Replication
    • None
    • ALL
    • Hide
      1. Start a 3 member replica set
      2. Stop all write activity
      3. Either:
        1. Restart one of the secondaries
        2. rs.remove and rs.remove one of the secondaries
      4. The restarted/removed&added secondary will display "could not find member to sync from" in the log file and does not display the "syncingTo" field in rs.status()
      Show
      Start a 3 member replica set Stop all write activity Either: Restart one of the secondaries rs.remove and rs.remove one of the secondaries The restarted/removed&added secondary will display "could not find member to sync from" in the log file and does not display the "syncingTo" field in rs.status()

      When a secondary replica member is either restarted or removed/added to a replica set it will display the following in the log file:

      2015-11-19T11:25:06.306-0500 I REPL     [ReplicationExecutor] could not find member to sync from

      It will also show either an error or no key/value for the rs.status() "syncingTo" field.

      This state remains until there is a write performed on the primary at which point a sync source is set.

      My expectation would be that we can set a sync source regardless of write activity under normal conditions given there is a primary.

            Assignee:
            Unassigned Unassigned
            Reporter:
            james.wahlin@mongodb.com James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: