[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: |
|
||||||||||||||||
| 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: Transmits the migration session id together with the abort command and |