Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- PM-3364-Milestone-5

Assigned Teams:

Catalog and Routing
Operating System:
ALL

Disclaimer: the command is not currently exposed on the router and can only be directly called on shards. Once SERVER-80416 will expose cloneCollectionAsCapped, the problem will surface.

The cloneCollectionAsCapped command is currently unsafe because is does not properly serialize with concurrent DDLs on the same namespace and will be even more unsafe "tomorrow" (once unsharded collections will be tracked) because it only performs changes on the local catalog.

Purpose of this ticket is to fix such limitation. The new implementation could perform an aggregation to copy the documents and create the new capped collection. More details in this comment.

duplicates

SERVER-80416 Expose cloneCollectionAsCapped command via mongos

Backlog

is depended on by

SERVER-84482 cloneCollectionAsCapped must support unsplittable collections

Closed

SERVER-85435 Remove check for sharding in cloneCollectionAsCapped tests

Backlog

is duplicated by

SERVER-85917 covertToCapped and cloneToCapped commads do not serialize properly with other DDL operations in sharded cluster

Closed

related to

SERVER-86030 Temporarly disable convertToCapped and cloneToCapped in test fuzzer when running against sharded clusters

Closed

Assignee:: [DO NOT USE] Backlog - Catalog and Routing

Reporter:: Pierlauro Sciarelli

Participants:: [DO NOT USE] Backlog - Catalog and Routing, Pierlauro Sciarelli

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: Jan 18 2024 02:19:12 PM UTC

Updated:: Mar 11 2024 04:46:53 PM UTC

Resolved:: Mar 11 2024 04:46:52 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates