[SERVER-77429] Renaming a sharded collection can hit transaction limit Created: 24/May/23  Updated: 26/Oct/23

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-77140 config metadata format should use col... Closed
Related
is related to SERVER-76988 Abort the reshardCollection operation... Closed
is related to SERVER-77140 config metadata format should use col... Closed
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 3

 Description   

We use transaction to make changes on the config metadata when performing rename. However, the size of the transaction is also a function of the number of tags/zones of the collection being renamed.

Resharding also has a similar problem when it tries to swap out the original sharded collection with the new collection with the new shard key as it also uses transactions to perform the rename.


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