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

ReplSet primary's state sometimes get stuck following reconfig

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • 2.6.7
    • Replication
    • None
    • ALL

    Description

      In some scenarios, a reconfig operation can cause the primary to get "stuck" in an unelectable state. The node recovers following a restart. The characteristic log lines look like the following:

      2015-02-18T17:35:57.494-0500 [conn221] replSet info : additive change to configuration
      2015-02-18T17:35:57.494-0500 [conn221] replSet replSetReconfig new config saved locally
       
      ...
       
      2015-02-18T17:36:02.656-0500 [rsMgr] replSet error p != rs->self in checkNewState
      2015-02-18T17:36:02.656-0500 [rsMgr] replSet CURRENT_HOST:27017
      2015-02-18T17:36:02.656-0500 [rsMgr] replSet CURRENT_HOST:27017

      The hostnames in the final two lines are the same.

      Attachments

        Activity

          People

            schwerin@mongodb.com Andy Schwerin
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: