[SERVER-45908] Use explicit read concern in sharding test index consistency hook Created: 31/Jan/20 Updated: 29/Oct/23 Resolved: 12/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: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2020-02-10, Sharding 2020-02-24 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 50 | ||||||||
| Description |
|
When shutting down a ShardingTest, a hook is run that verifies the indexes for each sharded collection exist on all shards with chunks for that collection. The hook uses an aggregation and find, but doesn't specify a read concern for either, so it would inherit a cluster wide default read concern if one is set, potentially leading to unexpected results. Instead the hook should use explicit read concerns. |
| Comments |
| Comment by Githook User [ 12/Feb/20 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |