Granular locks for synchronizing orphans tracking

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.0-rc4, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v6.0
    • Sharding EMEA 2022-05-02
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-64163 introduced a generic lock on the range-deleter collection for synchronizing orphans update and range deletions. Purpose of this ticket is to implement a more granular locking mechanism in order to parallelize concurrent orphans updates and range deletions. The granularity could be at range level (very granular, lock by migrationId) or at least at collection level (less granular, lock by collection UUID).

              Assignee:
              Allison Easton
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: