Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
2.0.0-rc0
-
None
-
ALL
Description
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.
Attachments
Issue Links
- is related to
-
SERVER-9110 checkAuth can cause step down on Authentication failure
-
- Closed
-
- related to
-
SERVER-15077 remove authissue/blockSync logic
-
- Closed
-