[SERVER-5888] Warn when replicasetmonitor detects different isMaster configurations when re-checking a replica set Created: 21/May/12 Updated: 06/Mar/14 Resolved: 06/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
The isMaster results should be consistent when we scan through the known hosts unless we're catching the replica set in the middle of a reconfig, or if the replica set is being affected by network segmentation. This isn't necessarily an error case, but it would be extremely helpful in certain cases to mark this occurring. |