[SERVER-80399] resharding should mark a collection as unsharded if called by unshardCollection Created: 24/Aug/23  Updated: 29/Oct/23  Resolved: 22/Sep/23

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

Type: Task Priority: Major - P3
Reporter: Kshitij Gupta Assignee: Kshitij Gupta
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-81138 Extend the test coverage over config.... Open
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02
Participants:

 Description   

This includes

  • marking the collection as unsplittable
  • drop all chunks and make a single chunk with _id shard key with the range pointing to the data bearing shard
  • refresh everywhere
  • changes should be done under a critical section
  • THEORETICALLY, resharding should give us most of this already
     
  • Also write a test for this


 Comments   
Comment by Githook User [ 21/Sep/23 ]

Author:

{'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}

Message: SERVER-80399: Set unsplittable field for moveCollection and unshardCollection.
Branch: master
https://github.com/mongodb/mongo/commit/61b078177c36e7b293f56e3b9bdda58a5ad55a91

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