[SERVER-60217] [v5.0] enableReconfigRollbackCommittedWritesCheck should be applied on 4.4 Created: 24/Sep/21  Updated: 29/Oct/23  Resolved: 02/Dec/21

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

Type: Bug Priority: Major - P3
Reporter: Vishnu Kaushik Assignee: Vishnu Kaushik
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-55376 Reconfig can roll back committed writ... Closed
is depended on by SERVER-57284 Wait for config commitment in reconfi... Closed
is depended on by SERVER-56919 Add validation for memberIndex to rec... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Replication 2021-11-29, Replication 2021-12-13
Participants:
Linked BF Score: 41

 Description   

We are currently removing the parameter enableReconfigRollbackCommittedWritesCheck for binaries before 5.0 (i.e. the 4.4 binary).

However, since SERVER-55376 has already been backported, this parameter should be applied.



 Comments   
Comment by Githook User [ 02/Dec/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-60217 remove last-continuous on 5.0, apply enableReconfigRollbackCommittedWritesCheck on 4.4, and re-enable disabled tests
Branch: v5.0
https://github.com/mongodb/mongo/commit/2073a238a879403d0cd57afbd7cc21348ca0e787

Comment by Githook User [ 02/Dec/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-60217 remove last-continuous binary testing
Branch: v5.0
https://github.com/10gen/mongo-enterprise-modules/commit/ada870010c5d283844a486513ddefb74b481b548

Comment by Githook User [ 17/Nov/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-60217 disable sync2.js and replsetarb2.js from multiversion suites
Branch: v5.0
https://github.com/mongodb/mongo/commit/507877a76dadbabd0155f4df2d099739de84d101

Comment by Judah Schvimer [ 27/Sep/21 ]

From triage meeting: Once 5.0 to 5.1 multiversion testing exists we should stop running 4.9 to 5.0 multiversion tests because 4.9 is not a user-facing release.

Comment by Vishnu Kaushik [ 24/Sep/21 ]

Reverting commits SERVER-56919, SERVER-57284, and SERVER-55376 on v4.4 until this ticket goes in. At the time of implementing this ticket, we should re-backport the above commits.

Comment by Vishnu Kaushik [ 24/Sep/21 ]

It looks like SERVER-55376 will have to be backported to 4.9 as well. This is because once we change the parameter in question to apply to all starting from 4.4 onwards, 5.0 multiversion tests that mix between the latest and last-continuous will try to pass in the parameter to the 4.9 (last-continuous) binary where it isn't defined yet.

Comment by Vishnu Kaushik [ 24/Sep/21 ]

See BF-22701 for more information.

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