ReplicationCoordinatorImpl::_handleHeartbeatResponse should check for cancelation before taking mutex

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • Repl 2019-05-06
    • 24
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Per ben.caimano's recent email, task executors are now more aggressive about running callbacks on callers' threads. This means that callbacks should check their provided status argument for whether they're on the caller's thread.

      _handleHeartbeatResponse takes the same mutex that its caller takes. If it runs on the caller's thread, it will deadlock with itself.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Spencer Jackson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: