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

Primary switches to Secondary because a new term has begun

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.18
    • Component/s: Replication
    • Labels:
      None
    • ALL

      After upgrading to 3.2.18 (from 3.2.11) on RHEL7.1, we intermittently see Primary switching to backup because a new term has begun.
      Secondary logs show that "Starting an election, since we've seen no PRIMARY in the past 10000ms" even though there is not network connectivity problem during that time.

        1. primary_log.txt
          4 kB
        2. rs_conf_log.txt
          2 kB
        3. rs_status_log.txt
          3 kB
        4. Screen Shot 2018-04-27 at 5.18.56 PM.png
          Screen Shot 2018-04-27 at 5.18.56 PM.png
          171 kB
        5. Screen Shot 2018-04-27 at 5.48.20 PM.png
          Screen Shot 2018-04-27 at 5.48.20 PM.png
          72 kB
        6. secondary_log.txt
          6 kB

            Assignee:
            arnie.listhaus@mongodb.com Arnie Listhaus
            Reporter:
            darshan.shah@interactivedata.com Darshan Shah
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: