Audit all callers of all catalog manager methods to make sure they are handling network errors

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.8
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 8 08/28/15
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      With the legacy catalog manager network errors become exceptions. In the replset catalog manager, network errors get reported as non-ok Statuses. We need to audit all callers of all catalog manager methods to make sure that they aren't relying on an exception to be thrown to catch network exceptions.

            Assignee:
            Spencer Brody (Inactive)
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: