[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: |
|
||||
| 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. |
| Comments |
| Comment by Githook User [ 23/Jan/20 ] |
|
Author: {'email': 'kevin.pulo@mongodb.com', 'username': 'devkev', 'name': 'Kevin Pulo'}Message: |
| 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? |