[SERVER-52802] [Resharding] Remove kDropping from the coordinator and donor Created: 11/Nov/20  Updated: 29/Oct/23  Resolved: 24/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-52801 Implement a local drop on resharding ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-11-30
Participants:

 Description   

kDropping isn't needed. Here's why:

  1. On shards that are only donors, they can instead drop on kRenaming.
  2. On shards that are donors and recipients, the drop happens as part of the local rename operation.

As part of this ticket, it's reasonable to assume that kDropping on the donor should be replaced with kRenaming. As part of this ticket, assess if that makes sense, and take action based on the assessment.

This ticket must be done before SERVER-52801. SERVER-52801 will handle the local dropping with donor-only shards and intra-shard synchronization with shards that are both donors and recipients.



 Comments   
Comment by Githook User [ 24/Nov/20 ]

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-52802 Remove kDropping from the ReshardingCoordinator
Branch: master
https://github.com/mongodb/mongo/commit/5f72078a11a072b2af8cae30b195038945e49755

Generated at Thu Feb 08 05:29:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.