[SERVER-46173] Disable index consistency check in shard_removal_triggers_catalog_cache_invalidation.js Created: 14/Feb/20 Updated: 29/Oct/23 Resolved: 14/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: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2020-02-24 | ||||
| Participants: | |||||
| Linked BF Score: | 37 | ||||
| Description |
|
shard_removal_triggers_catalog_cache_invalidation.js uses two routers, removes a shard using one of them, shuts down the shard, then waits for the other router to reload its shard registry and stop targeting the removed shard. The index consistency shutdown hook runs commands on the first router, which isn't guaranteed to have reloaded its shard registry and may fail to target the shut down shard, failing the test. To avoid this, the index hook should be disabled. |
| Comments |
| Comment by Githook User [ 14/Feb/20 ] |
|
Author: {'username': 'jsmulrow', 'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |