[SERVER-76482] Move execution of 'checkShardFilteringMetadata' hook in ShardingTest Created: 25/Apr/23 Updated: 29/Oct/23 Resolved: 26/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-05-01 |
| Participants: |
| Description |
|
ShardingTest executes the 'checkShardFilteringMetadata' hook after having first executed 'checkUUIDsConsistentAcrossCluster'. 'checkUUIDsConsistentAcrossCluster' may cause the shard to artificially refresh its filtering metadata. This may cover some failures that the 'checkShardFilteringMetadata' would have detected. |
| Comments |
| Comment by Githook User [ 26/Apr/23 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |