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

Secondary became primary through election when secondary can not find primary.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 3.2.8
    • Replication
    • None
    • ALL
    • Hide

      Don't konw.

      Show
      Don't konw.

    Description

      Before this time, many time-consuming operations happened at the primary node

      Secondary log:
      2018-07-26T04:01:00.023+0000 I REPL [ReplicationExecutor] Error in heartbeat request to 10.0.189.100:27017; ExceededTimeLimit: Operation timed out
      2018-07-26T04:01:04.254+0000 I REPL [ReplicationExecutor] stepping down from primary, because a new term has begun: 98
      2018-07-26T04:01:04.322+0000 I REPL [replExecDBWorker-1] transition to SECONDARY
      2018-07-26T04:01:05.413+0000 I REPL [ReplicationExecutor] Member 10.0.189.100:27017 is now in state PRIMARY

      I have archived (tar or zip) the $dbpath/diagnostic.data directory from each node.

      Attachments

        1. backup.zip
          6.44 MB
        2. primary.zip
          3.43 MB
        3. secondary.zip
          8.73 MB

        Activity

          People

            nick.brewer Nick Brewer
            cuizihang Zihang Cui
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: