[SERVER-81799] Batch the transactions in the commit of movePrimary Created: 03/Oct/23  Updated: 28/Nov/23  Resolved: 28/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Backlog - Catalog and Routing
Resolution: Won't Do Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-79668 Move primary must be compatible with ... Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

When featureFlagTrackUnshardedCollectionsOnShardingCatalog is enabled, the commit of movePrimary on the config server needs to update the chunk entry for each unsharded collection that is located on the prior dbPrimary. If there are many collections in the database, this could make the transaction exceed the size limit for transactions.

We should split this transaction into batches so that we are sure we won't exceed the max transaction size.



 Comments   
Comment by Pierlauro Sciarelli [ 28/Nov/23 ]

Closing as "won't do" because the new movePrimary logic will never make it to production:

  • In v7.3 we will not track yet unsharded collections
  • In v8.0 movePrimary is going to be deprecated
Generated at Thu Feb 08 06:47:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.