[SERVER-79668] Move primary must be compatible with unsplittable collections Created: 03/Aug/23  Updated: 22/Jan/24  Resolved: 05/Oct/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: PM-3364-Milestone-2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-80891 Change the catalog client to support ... Closed
is depended on by SERVER-81799 Batch the transactions in the commit ... Closed
Problem/Incident
causes SERVER-85524 Re-enable analyze_shard_key_database_... Backlog
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Participants:

 Description   

One of the steps of move primary in the commit phase is to update the new database primary shard, now we need to also transactionally change all chunks belonging to unsplittable collections to the new destination shard.



 Comments   
Comment by Githook User [ 05/Oct/23 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-79668 Move primary must be compatible with unsplittable collections
Branch: master
https://github.com/mongodb/mongo/commit/52c53e1b32b8a0bb58346465dbe23c843357cf3b

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