Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2024-12-09
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

As we introduce new test files within the core_sharding folder, we'll need to ensure that the cluster topology instantiated by each suite is consistent with the one expected by each test case.

While SERVER-96953 will eventually introduce an automated and scalable way to enforce topology-bound constraints between suites and tests, we need at least the existence of a requires_2_or_more_shards exclusion tag to address the most urgent needs.

depends on

SERVER-97627 Ensure the existence of one or more test suites executing the content of 'core_sharding' and provisioning a 2-shard cluster

Closed

related to

SERVER-91143 Enhance the core_sharding passthrough suite for tests requiring a minimum set of routers and/or shards

Backlog

SERVER-96953 Allow resmoke to generate exclusion test tags based on the topology of the running (sharded) cluster fixture.

Needs Scheduling

Assignee:: Tommaso Tocci
Reporter:: Paolo Polato
Participants:: Githook User, Paolo Polato, Tommaso Tocci
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Nov 26 2024 12:07:46 PM UTC
Updated:: Jul 23 2025 03:36:37 PM UTC
Resolved:: Dec 05 2024 07:01:08 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates