[SERVER-26077] Migration cloner abort does not validate the session id Created: 12/Sep/16  Updated: 04/Jan/17  Resolved: 13/Sep/16

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-25356 _recvChunkAbort should also send the ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.2
Sprint: Sharding 2016-09-19
Participants:
Linked BF Score: 0

 Description   

The migration cloner abort sequence does not transmit or validate the migration session id. Because of this it is possible that one shard aborts migration, which has been started by a completely different donor shard.

This bug is exacerbated in 3.3 because failure to execute the _recvChunkStart command is always followed-up by an abort. That way if two migrations with different donors, but the same recipient have the potential of conflicting with each other in which case one of the migrations will remain stuck.



 Comments   
Comment by Githook User [ 13/Sep/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-26077 Tighten checks around migration session id

Transmits the migration session id together with the abort command and
ensures that the migration session id reported in the status matches that
of the cloner.
Branch: master
https://github.com/mongodb/mongo/commit/0c8ffece21a601fe3861aba6cc191b2ce1be0f54

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