In certain situations it is illegal to wait for write concern, such as while holding X lock on the local database. We should tighten these assertions so we catch offending callers.
In addition, as part of this change we should not allow write concern other than majority for config servers.
- is duplicated by
-
SERVER-21723 Replica set nodes hang when awaiting replication in DBDirectClient
- Closed
- related to
-
SERVER-25468 Using DBDirectClient trips invariant failure about lock state in ReplicationCoordinatorImpl::waitUntilOpTimeForRead()
- Closed