[SERVER-48160] remove IndexBuildsCoordinator::_tryAbort() fatal assertion 4656001 for missing index build thread Created: 12/May/20 Updated: 29/Oct/23 Resolved: 15/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc10, 4.7.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||||||
| Sprint: | Execution Team 2020-05-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 18 | ||||||||||||||||||||
| Description |
|
Consider removing the fatal assertion for 4656001; or convert to a non-fatal user assertion. In IndexBuildsCoordinator::_tryAbort(), it is a fatal error if we are unable to look up the OperationContext of an index build to interrupt using the ReplIndexBuildState::opId (set at index build startup). This fatal assertion was originally introduced in This assertion does not really suggest a crash-worthy scenario because if the OperationContext for an index build cannot be found, it would mean that the index build has completed (committed or aborted) and there would not be any OperationContext to interrupt for the user-initiated abort request. |
| Comments |
| Comment by Githook User [ 12/Jun/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry picked from commit 38d66e6ba3e01b3fb817c655decd077c9d9d7b0d) |
| Comment by Githook User [ 14/May/20 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |