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

Avoid quadratic behavior in rollback with many collections

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 5.0.0
    • 5.2.0, 5.0.5, 5.1.1
    • Storage
    • None
    • Fully Compatible
    • v5.1, v5.0
    • Execution Team 2021-08-09, Execution Team 2021-11-01, Execution Team 2021-11-15
    • 153

    Description

      Copying the CollectionCatalog is expensive. When there are tens of thousands of collections, operations like rollback become substantially slower. When the server is rolling back to the stable timestamp, the global lock is held in exclusive mode. We should be able to avoid making multiple copies of the collection catalog.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-59065 CatalogStats uses unsafe CollectionCatalog pointer during startup

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-59591 LockerNoop::isW() always returns true allowing multiple operations think they are holding the global exclusive lock at the same time

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-59819 collection_catalog_bm setup causes timeout

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-60462 Global MODE_IS lock is required to access CollectionCatalog::get() in time-series code path

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

          Task - A task that needs to be done. SERVER-60460 Add invariant to check that global lock is held when calling CollectionCatalog::get

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-62618 Avoid quadratic behavior at startup with many collections

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

          Activity

            People

              henrik.edin@mongodb.com Henrik Edin
              gregory.wlodarek@mongodb.com Gregory Wlodarek
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: