[SERVER-14567] Implement checkIfWriteConcernCanBeSatisfied Created: 15/Jul/14  Updated: 02/Aug/18  Resolved: 15/Sep/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.7.3
Fix Version/s: 2.7.7

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-15332 cleanupOrphaned deletes a document, ... Closed
Related
related to SERVER-14041 enhance secondaryThrottle parameter Closed
is related to SERVER-18407 Ensure getLastErrorDefaults/getLastEr... Closed
Participants:

 Description   

/**
 * 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.



 Comments   
Comment by Githook User [ 15/Sep/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-14567 Implement checkIfWriteConcernCanBeSatisfied in ReplicationCoordinatorImpl
Branch: master
https://github.com/mongodb/mongo/commit/fdfcb2b6922bcd64982659f82f1a47cc31de7929

Generated at Thu Feb 08 03:35:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.