[SERVER-26189] The Balancer's operation context is not getting interrupted at stepdown Created: 20/Sep/16 Updated: 19/Nov/16 Resolved: 20/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: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2016-10-10 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
When a stepdown happens, the balancer's operation context is not getting marked as interrupted, which means that if it happen to wait on read concern or any other interruptible call, it will get stuck. This causes problems when that that same node is becoming primary again, because it will deadlock trying to join the already stuck balancer thread. |
| Comments |
| Comment by Githook User [ 20/Sep/16 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |