[SERVER-49423] Do not set coordinateCommitReturnImmediatelyAfterPersistingDecision in change stream multiversion suites Created: 10/Jul/20  Updated: 29/Oct/23  Resolved: 16/Oct/20

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

Type: Task Priority: Major - P3
Reporter: Bernard Gorman Assignee: Bernard Gorman
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-51682 Remove special-case handling of coord... Closed
is related to SERVER-37364 Coordinator should return the decisio... Closed
is related to SERVER-47890 Unblacklist report_post_batch_resume_... Closed
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 50

 Description   

SERVER-47890 fixed some issues and allowed us to set the new server parameter coordinateCommitReturnImmediatelyAfterPersistingDecision to true for change stream suites following its introduction in SERVER-37364. However, since this server parameter only exists in master, the generated change stream multiversion suites are failing when 4.4 nodes attempt to set this server parameter.

Ideally we don't want to disable the multiversion suites or lose coverage of this new server parameter. One solution might be to remove the server parameter from the standard change streams suites and add a new passthrough which sets it. Then the multiversion suites would not use the parameter, and we would have coverage of the change stream suites both with the parameter set to true and omitted (thereby defaulting to false).



 Comments   
Comment by Githook User [ 16/Oct/20 ]

Author:

{'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}

Message: SERVER-49423 Do not set coordinateCommitReturnImmediatelyAfterPersistingDecision in change stream multiversion suites
Branch: master
https://github.com/mongodb/mongo/commit/19bef363124a342208b7ba6cdb558285427e78e0

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