DBConnectionPool doesn't return code `ShutdownInProgress` when it is being shut down

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.0-rc0
    • Affects Version/s: 3.4.9, 3.5.13
    • Component/s: Networking
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-10-02
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Some sharding code paths (such as migration commit) rely on a shutdown code to be specified in order to gracefully terminate.

      The DBConnectionPool stops working when the server starts the shutdown sequence, but returns code 17382, which cannot be used to infer a shutdown.

      We should make it return a ErrorCodes::ShutdownInProgress instead.

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: