Hold critical section in resharding coordinator between global catalog commit and shard catalog section

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • 3
    • 🟥 DDL, 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the critical section is not held which leads to a existence of a time window, that allows the following scenario to appear:

      Example of hitting similar issue in production was noticed in SERVER-134127 which led to exclusion of certain checks from jstests to avoid the problem causing BFs.

      Note, that this can be abused only for temporary resharding collections, which are not directly visible by users. Therefore it doesn't produce a direct impact exposed to the users. Additionally, the issue does resolve after eventually the recipient fetches the data from the global catalog.

      Therefore we should seek to obtain a critical section during this time window and ensure this problem won't surface again.

            Assignee:
            Unassigned
            Reporter:
            Rustam Gusein-zade
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: