-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.7.3
-
Component/s: Replication
-
None
/** * Checks if the current replica set configuration can satisfy the given write concern. * * Things that are taken into consideration include: * 1. If the set has enough members. * 2. If the tag exists. * 3. If there are enough members for the tag specified. */ virtual Status checkIfWriteConcernCanBeSatisfied( const WriteConcernOptions& writeConcern) const = 0;
Note: LegacyReplicationCoordinator::checkIfWriteConcernCanBeSatisfied has a rough implementation that should be replaced.
- is duplicated by
-
SERVER-15332 cleanupOrphaned deletes a document, and then returns error, when writeConcern references non-existent tagset
- Closed
- is related to
-
SERVER-18407 Ensure getLastErrorDefaults/getLastErrorModes are satisfiable
- Closed
- related to
-
SERVER-14041 enhance secondaryThrottle parameter
- Closed