[SERVER-9110] checkAuth can cause step down on Authentication failure Created: 25/Mar/13 Updated: 10/Dec/14 Resolved: 28/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Eric Milkie |
| Resolution: | Cannot Reproduce | Votes: | 6 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Manager::checkAuth in manager.cpp will cause a Primary to step down if there is an auth failure, and no nodes are marked as up. This is primarily during a reconfig so that the authentication problem would get attention from the user - however it has also been seen to bring down a otherwise functioning Primary in a replica set. There doesn't seem to be a benefit to stepping down on auth errors, especially in the case were a node has been operational as Primary for some time. |
| Comments |
| Comment by Eric Milkie [ 28/May/13 ] |
|
I was unable to find any failure case for version 2.4, where the reconnect and auth code was significantly rewritten. |
| Comment by Eric Milkie [ 08/May/13 ] |
|
Due to |
| Comment by Eric Milkie [ 25/Mar/13 ] |
|
I'd like to treat inaccessible secondaries the same as unreachable secondaries. |