[SERVER-45638] Require majority read concern enabled in read_write_concern_defaults_application Created: 17/Jan/20  Updated: 29/Oct/23  Resolved: 23/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Kevin Pulo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-01-27
Participants:
Linked BF Score: 50

 Description   

The test shading/read_write_concern_defaults_application fails when its running on the variants wit disabled majority read concern.
It needs a requires_majority_read_concern tag



 Comments   
Comment by Githook User [ 23/Jan/20 ]

Author:

{'email': 'kevin.pulo@mongodb.com', 'username': 'devkev', 'name': 'Kevin Pulo'}

Message: SERVER-45638 add tags for RCM and text logs to read_write_concern_defaults_application.js
Branch: master
https://github.com/mongodb/mongo/commit/514531299ee6c275e6b40e0b881c7bf41996e90d

Comment by Kevin Pulo [ 20/Jan/20 ]

Yep — unless I'm misunderstanding it, I think it's literally just adding the tag to the test. This will stop it from running in the RCM disabled variants, since it doesn't need to run there because the regular (ie. RCM enabled) coverage is sufficient. So the bug is that the test ought to declare that it requires readConcern majority, but is missing the tag to do that.

Comment by Kaloian Manassiev [ 20/Jan/20 ]

CC kevin.pulo - this is the ticket that we were talking about this morning and you said it's a simple fix, right?

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