Do not acquire the dist lock in CSRS on RefineShardKey after 5.0

XMLWordPrintableJSON

    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      After 5.0 has branched out, the ConfigsvrRefineCollectionShardKeyCommand will just be receivable from the primary shard already holding the lock, hence the changes introduced in SERVER-54809 can be thrown away.

            Assignee:
            Tommaso Tocci
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: