[SERVER-52759] Fit 'moveChunk' in the DDL coordinator/participant model Created: 11/Nov/20  Updated: 06/Dec/22  Resolved: 04/May/21

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Fix Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-54856 Add a test with concurrent moveChunk ... Closed
Related
is related to SERVER-54881 Ensure new DDL FSMs work with balance... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

This ticket is for the following work:

  • Theoretically prove that moveChunk and concurrent DDL cannot run at the same time and either crash or leave garbage (the collection distributed lock plus the allowMigration fields should ensure that)
  • Enable the balancer and auto-splitter in the DDL FSM workloads


 Comments   
Comment by Kaloian Manassiev [ 04/May/21 ]

We won't be creating a DDL coordinator for moveChunk. The synchronisation is already taken care of by the distributed lock. Closing this ticket and the testing work will be done under the linke SERVER-54881.

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