[SERVER-51682] Remove special-case handling of coordinateCommitReturnImmediatelyAfterPersistingDecision for multiversion suites Created: 16/Oct/20  Updated: 26/Aug/21  Resolved: 26/Aug/21

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Bernard Gorman Assignee: Bikash Chandra (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-48645 Remove versioning constraints on test... Closed
Related
is related to SERVER-49423 Do not set coordinateCommitReturnImme... Closed
Sprint: QE 2021-09-06
Participants:

 Description   

In SERVER-49423, we added special-case handling for the scenario where a suite attempts to explicitly set the coordinateCommitReturnImmediatelyAfterPersistingDecision parameter on a 4.4 mongoD. This is not available prior to 4.7, so we simply remove it from the parameters list. When 5.0 becomes last-lts, the elif clause in the linked code block should be removed.



 Comments   
Comment by Rushan Chen [ 25/Aug/21 ]

Also the check "executable != LAST_LTS_MONGOD_BINARY" is no longer needed as the coordinateCommitReturnImmediatelyAfterPersistingDecision is supported with the LTS now bumped up to 5.0.

 

Generated at Thu Feb 08 05:26:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.