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

Avoid checking _checkIfWriteConcernCanBeSatisfied_inlock in ReplicationCoordinatorImpl::_doneWaitingForReplication_inlock

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2019-10-07

      The answer to _checkIfWriteConcernCanBeSatisfied_inlock is rarely changed unless a replSetReconfig happens. Thus, it is more efficient to avoid checking that in ReplicationCoordinatorImpl::_doneWaitingForReplication_inlock. Instead, we should change ReplicationCoordinatorImpl::_setCurrentRSConfig to wake up waiters with ERROR if their writeConcern can no longer be satisfied.

            Assignee:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: