[SERVER-24470] Check in CommitChunkMigration that the distlock is held Created: 08/Jun/16  Updated: 02/Sep/16  Resolved: 29/Aug/16

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-24781 DistLockManager on the CSRS primary s... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-08-29, Sharding 2016-09-19
Participants:

 Description   

Currently the moveChunk command double checks that it still holds the distlock before entering the critical section of a migration. SERVER-22658 will make the balancer take the lock, and the shard no longer has the distlock to check. CommitChunkMigration should thereafter check the distlock.



 Comments   
Comment by Githook User [ 29/Aug/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-24470 CommitChunkMigration command checks that the balancer still has the distributed lock
Branch: master
https://github.com/mongodb/mongo/commit/2374ef1a3ac05e3fca39485ef4824f559b1c082c

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