[SERVER-3459] isMaster reports secondary == false when a node is recovering Created: 21/Jul/11 Updated: 22/Jul/11 Resolved: 22/Jul/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Ryan Nitz | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
If a node in a replica set is marked as "RECOVERING" it is not marked as a secondary in the isMaster. This might break the drivers, but theoretically, it should display itself as a secondary because only a secondary can recover. E.g. "isMaster": { "hosts": [ "server1.cc:27018", "server2:27018", "server3:27018" ], "ismaster": false, "maxBsonObjectSize": 16777216, "ok": 1, "primary": "server1:27018", "secondary": false, "setName": "myset" } |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 22/Jul/11 ] |
|
secondary=true means it is allowed to be queries as a secondary. |