[SERVER-48055] Disable periodic index consistency check in index_commands_shard_targeting Created: 08/May/20  Updated: 06/Dec/22  Resolved: 05/Jun/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-48096 PeriodicShardedIndexConsistencyChecke... Closed
Related
Assigned Teams:
Sharding
Operating System: ALL
Participants:
Linked BF Score: 44

 Description   

This test asserts that a shard does not have the latest metadata for a sharded collection, but this assertion can fail if the periodic index consistency check triggers a refresh at the right time. The periodic check should be disabled using the enableShardedIndexConsistencyCheck server parameter. The parameter should be set at startup to avoid failures in the config server stepdown suite.



 Comments   
Comment by Max Hirschhorn [ 05/Jun/20 ]

Closing this ticket as a duplicate of SERVER-48096 because we'll address unintended shard refreshes by disabling the PeriodicShardedIndexConsistencyChecker in the sharding_continuous_config_stepdown.yml test suite.

Generated at Thu Feb 08 05:16:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.