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.