[SERVER-25344] Race between MigrationDestinationManager thread startup and abort Created: 29/Jul/16 Updated: 13/Aug/16 Resolved: 30/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.10 |
| Fix Version/s: | 3.3.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 18 (08/05/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
If the donor of a chunk requests the recipient to start migration, but immediately terminates and sends an abort request, it is possible that this abort will run before the migration thread is scheduled and will trigger an invariant failure getState() == READY. |
| Comments |
| Comment by Githook User [ 30/Jul/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |