[SERVER-73396] Balancer should be stopped before running CheckShardFilteringMetadata Created: 27/Jan/23 Updated: 29/Oct/23 Resolved: 14/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding EMEA 2023-02-20 | ||||
| Participants: | |||||
| Linked BF Score: | 21 | ||||
| Description |
|
CheckShardFilteringMetadata requires the balancer to be stop in order to be able to perform its checks. This is usually the case because previous hooks already stop it (e.g. this one here). However, if previous hooks are skipped (as is the case for 'checkOrphansAreDeleted' on the sharding_continuous_config_stepdown suite), then CheckShardFilteringMetadata will end up running with balancer enabled. This ticket is to ensure CheckShardFilteringMetadata is always run with balancer stopped. |
| Comments |
| Comment by Githook User [ 14/Feb/23 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |