Issue clear error if can't connect to all machines from a shard

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Each shard must be able to talk to all config servers and at-least one member of each shard's replicaSet. If a user has overzealous firewall rules things will break and the only error will be 10276: "DBClientBase::findOne: transport error".

      Perhaps we should have a background job try to connect to everyone once a minute and warn if it can't.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Mathias Stearn
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: