Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
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

convertToCapped and cloneToCapped commands do not work properly in sharded cluster with tracked collections due to ~~SERVER-85372~~ and ~~SERVER-84482~~.

The goal of this ticket is to temporarily prevent the mutational fuzzer to use this command when running against sharded clusters.

is depended on by

SERVER-81190 Support tracking "simple" unsharded collections in the sharding catalog

Closed

is related to

SERVER-84482 cloneCollectionAsCapped must support unsplittable collections

Closed

SERVER-85372 Make cloneCollectionAsCapped work properly in case of concurrent DDLs

Closed

related to

SERVER-86031 Re-enable convertToCapped and cloneCollectionAsCapped in test fuzzer in sharded clusters

Blocked

Assignee:: Tommaso Tocci
Reporter:: Tommaso Tocci
Participants:: Tommaso Tocci
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jan 31 2024 06:21:34 PM UTC
Updated:: Apr 03 2025 01:54:17 PM UTC
Resolved:: Feb 13 2024 02:11:53 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates