[SERVER-20412] the _priorityTakeover CallbackHandle does not reset properly when cancelled Created: 15/Sep/15 Updated: 07/Oct/15 Resolved: 15/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.1.8 |
| Fix Version/s: | 3.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Dannenberg | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | RPL 9 (09/18/15) |
| Participants: |
| Description |
|
When the callback is cancelled, we do not replace the CallbackHandle with a new null one. As a result, the CallbackHandle is still valid and we will not schedule a new priorityTakeover until the cancelled one executes. |
| Comments |
| Comment by Githook User [ 15/Sep/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |