Clean up unnecessary mutex acquisitions in tenant migration recipient service

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We do not need to hold the tenant migration recipient service mutex while reading the state doc in the main chain. It should be impossible for another thread to be changing _stateDoc. 

      reportForCurrentOp requires the mutex before reading the _stateDoc because the operation comes from a user thread. 

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: