Warn when replicasetmonitor detects different isMaster configurations when re-checking a replica set

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Sharding
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Unassigned
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: