[SERVER-25086] Remove distlock acquisition from split and merge chunk Created: 15/Jul/16  Updated: 06/Dec/22  Resolved: 14/Oct/19

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 2
Labels: PM-584, splitNoDistlock
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-27724 Explore whether we can further minimi... Closed
related to SERVER-44201 Complete TODO listed in SERVER-25086 Closed
Assigned Teams:
Sharding
Participants:

 Comments   
Comment by Githook User [ 05/Dec/19 ]

Author:

{'name': 'Tommaso Tocci', 'username': 'toto-dev', 'email': 'tommaso.tocci@10gen.com'}

Message: SERVER-44201 Remove outdated TODO note

The TODO refers to SERVER-25086 that have been marked as
won't fix.
Branch: master
https://github.com/mongodb/mongo/commit/3232fb0d0ada81eaee63c02887f6639284da1905

Comment by Ratika Gandhi [ 14/Oct/19 ]

Closing this because autosplitter no longer blocks writes in 4.2
cc. josef.ahmad, do you have any other concerns? 

Comment by Kaloian Manassiev [ 07/Oct/19 ]

Thanks Josef for bringing this ticket up. I believe the original problems with removing the dist lock acquisitions during split and merge was not around who owns the auto-splitter, but that about the lack of other synchronisation between these two operations and moveChunk (in addition to also drop collection).

I am pulling it into 'Needs Triage' so we can discuss it at the next team triage meeting.

Comment by Josef Ahmad [ 04/Oct/19 ]

Given that the shard owns the autosplitting starting from 4.2, is there any other dependency for this ticket?

Generated at Thu Feb 08 04:08:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.