[SERVER-75820] Investigate why shard filtering metadata hook fails in catalog shard tests Created: 07/Apr/23  Updated: 29/Oct/23  Resolved: 01/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc1

Type: Task 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:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0
Sprint: Sharding NYC 2023-04-17, Sharding NYC 2023-05-01, Sharding NYC 2023-05-15
Participants:

 Description   

Two catalog shard tests fail the checkShardFilteringMetadata hook at ShardingTest shutdown. Both fail because a secondary does not have filtering metadata in its shardingState response, and both involve either adding a shard or reconfiguring a node into a shard near the end of the test, so this may be the expected behavior, but we should verify this.

jstests/sharding/reconfig_fails_no_cwwc_set_sharding.js

jstests/sharding/implicit_default_write_concern_add_shard.js



 Comments   
Comment by Githook User [ 01/May/23 ]

Author:

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

Message: SERVER-75820 Skip checkShardFilteringMetadata hook in some config shard tests

(cherry picked from commit a339ccb0096be6800af8b263cc63d239ad7fe6da)
Branch: v7.0
https://github.com/mongodb/mongo/commit/8dfde73af92f6ec9a15d6cfdcc4a0c854e4b81f8

Comment by Githook User [ 28/Apr/23 ]

Author:

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

Message: SERVER-75820 Skip checkShardFilteringMetadata hook in some config shard tests
Branch: master
https://github.com/mongodb/mongo/commit/a339ccb0096be6800af8b263cc63d239ad7fe6da

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