secondary mongod report "changing sync target" in log file

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      we deploy one replicaset with three machines running mongod(one primary, two secondary). These machines have 10Gbps ethernet bandwidth for mongodb ,and SSD card for mongodb datafile. data items for db to handle are totally 41000000 per week. When replication runs a long time, the two secondary mongod reports "changing sync target because current sync target's most recent OpTime is Jan 4 19:47:18:230 which is more than 30 seconds behind member 172.28.11.142:27017 whose most recent OpTime is 1451908070"

            Assignee:
            Unassigned
            Reporter:
            leipei
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: