[SERVER-46000] Unset default read concern at end of read_write_concern_defaults_startup.js Created: 05/Feb/20  Updated: 29/Oct/23  Resolved: 06/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
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-02-10
Participants:
Linked BF Score: 50

 Description   

This test sets the default read concern to majority which causes the ShardingTest index consistency shutdown hook to use majority read concern for an aggregation, triggering a failure when majority read concern is disabled. The test should unset the default before shutting down to avoid this.



 Comments   
Comment by Githook User [ 06/Feb/20 ]

Author:

{'username': 'jsmulrow', 'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-46000 Unset default read concern between test cases in read_write_concern_defaults_startup.js
Branch: master
https://github.com/mongodb/mongo/commit/5dbd3cad67e486f6612ed5d0060669b2aa19dc13

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