Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-78259

Revise strong lock acquisitions on the chunk migrations code path

    • Cluster Scalability
    • ALL

      As part of the work to support distributed transactions (under SERVER-38147) we decided to cap the donor strong lock acquisitions to 500ms by default in order to avoid shard-wide stalls due to strong locks being stuck behind active transactions (which can possibly have longer duration). The consideration is that while customers have control of when to issue a DDL operation which may take a strong lock, they have no control of when the balancer decides to move chunk.

      This ticket is to consider the same for the recipient side of chunk migration. Specifically we have the following acquisitions:
      Prior to 4.4:

      • Indexes reconciliation between donor and recipient here
      • Updating the range deleter state here

      After 4.4 only the first one remains.

            nandini.bhartiya@mongodb.com Nandini Bhartiya
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            0 Vote for this issue
            5 Start watching this issue