Resumed create coordinator may incorrectly try to release the critical section

XMLWordPrintableJSON

    • Fully Compatible
    • v6.1, v6.0, v5.0
    • Sharding EMEA 2022-10-31
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It may happen that a create collection coordinator successfully commits the metadata of a new sharded collection on the config server (here or here) and releases the critical section right before stepping down. On resume, the collection is identified as already sharded and the critical section re-released. However, if a migration kicks in and acquires the critical section right before issuing the release, the following invariant is triggered.

              Assignee:
              Enrico Golfieri
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: