[SERVER-66858] collection_uuid_index_commands.js fails when shard is unavailable Created: 30/May/22  Updated: 01/Jun/22  Resolved: 01/Jun/22

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Gregory Noma
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-65234 collection_uuid_index_commands test s... Closed
Sprint: Execution Team 2022-06-13
Participants:
Linked BF Score: 20

 Description   

collection_uuid_index_commands.js expects all shards to fail dropIndexes with CollectionUUIDMismatch in a sharded cluster.
However, in some suites, multi_shard_multi_stmt_txn_kill_primary_jscore_passthrough.yml for example, the primary is not always readily available. This means dropIndexes may fail with HostUnreachable if one of the shards doesn't have a primary instead of CollectionUUIDMismatch, causing the test to fail.

The test could be made to accept HostUnreachable from shards when there is no primary on said shard, or be disallowed from running with failovers


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