[SERVER-39221] Test rollback after enableMajorityReadConcern upgrade/downgrade Created: 28/Jan/19  Updated: 29/Oct/23  Resolved: 19/Mar/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.10, 4.0.10

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
is documented by DOCS-12560 Docs for SERVER-39221: Test rollback ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Repl 2019-02-25, Repl 2019-03-11, Repl 2019-03-25
Participants:

 Description   

We have coverage for toggling enableMajorityReadConcern in disable_majority_reads_restart.js. However, we do not have coverage for rollbacks after toggling. We should add test coverage to determine what the behavior is and decide whether the behavior is acceptable.



 Comments   
Comment by Githook User [ 16/Apr/19 ]

Author:

{'name': 'Tess Avitabile', 'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com'}

Message: SERVER-39221 Test rollback after enableMajorityReadConcern upgrade/downgrade
Branch: v4.0
https://github.com/mongodb/mongo/commit/9d633ef1ff7d7f51cfecf831b9ae549290ac80a6

Comment by Githook User [ 19/Mar/19 ]

Author:

{'name': 'Tess Avitabile', 'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com'}

Message: SERVER-39221 Test rollback after enableMajorityReadConcern upgrade/downgrade
Branch: master
https://github.com/mongodb/mongo/commit/ec1e10dc518b36d381faeb228008512f0dee68c4

Generated at Thu Feb 08 04:51:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.