[SERVER-86030] Temporarly disable convertToCapped and cloneToCapped in test fuzzer when running against sharded clusters Created: 31/Jan/24  Updated: 01/Feb/24

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-81190 Support tracking "simple" unsharded c... Closed
Related
related to SERVER-86031 Re-enable convertToCapped and cloneCo... Blocked
is related to SERVER-85372 Make cloneCollectionAsCapped and conv... Open
is related to SERVER-84482 convertToCapped and cloneCollectionAs... Blocked
Assigned Teams:
Catalog and Routing
Participants:

 Description   

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.


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