Change DistLock initialization so each node in a shard will have the same ID when locking

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2020-11-30
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When initializing the shard components, a new ID is generated for the distributed lock, however, if a primary node holds a lock and a stepdown happens, then when trying to hold a lock over the same resource (when retrying the operation) will fail.

      As part of the PM-1965 project, the shardCollection command will be moved to the primary, and the current behavior will not allow this necessary change.

            Assignee:
            Marcos José Grillo Ramirez
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: