re-adding member to replica set without keyFile results in secondary node

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.0.2, 2.1.0
    • Affects Version/s: 2.0.0-rc0
    • Component/s: Replication
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a replica set is started with authentication via a key file, and a member is shut down and restarted without a key file, the member will eventually rejoin the replica set and become a SECONDARY member, even though (it appears) that the oplog and database are empty. Queries could get routed to these nodes with weird effects.

      Invalid key files result in a RECOVERING state, which is probably correct.

              Assignee:
              Kristina Chodorow (Inactive)
              Reporter:
              Greg Studer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: