[SERVER-47536] Investigate behavior of sending a killop to an index builder thread and state transitions Created: 14/Apr/20 Updated: 29/Oct/23 Resolved: 04/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2020-05-04, Execution Team 2020-06-01, Execution Team 2020-06-15 |
| Participants: |
| Description |
|
After The behavior under normal circumstances is that the index builder will corrrectly-self destruct and clean up, however we should investigate what happens when a node step-down interleaves with this operation. |
| Comments |
| Comment by Githook User [ 04/Jun/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 04/Jun/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Louis Williams [ 14/Apr/20 ] |
|
I have a suspicion (and hope) that the resulting behavior ends up like this test where sending a killop to the index builder thread on a secondary crashes the server and the node must restart. We should explore if there is a cleaner way to do this. |