Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-48264

ShardServerCatalogCacheLoader doesn't handle threadpool shutdown

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.7.0
    • Sharding
    • Fully Compatible
    • ALL
    • Sharding 2020-08-10
    • 20

    Description

      The ShardServerCatalogCacheLoader lambdas when scheduling work on the _threadPool immediately invariant that the status is OK. This is incorrect, because it means that they can't handle the situation where the threadpool is shutting down,which results in the lambda being immediately calling in-line with a status of ShutdownInProgress.

      These lambdas should instead handle this situation properly, eg. by changing the invariant to a uassert and moving it inside the try block, or how other ThreadPool users do it.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-47972 maxTimeMS set on hedged requests does not give shards enough time to refresh

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-39965 Make OutOfLineExecutor return a Status from schedule()

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              randolph@mongodb.com Randolph Tan
              kevin.pulo@mongodb.com Kevin Pulo
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: