[SERVER-45905] abortIndexBuild oplog entry should ignore NamespaceNotFound errors Created: 31/Jan/20 Updated: 29/Oct/23 Resolved: 31/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| Resolution: | Fixed | 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: | Execution Team 2020-02-10 | ||||||||
| Participants: | |||||||||
| Description |
|
abortIndexBuild should ignore NamespaceNotFound errors for idempotency reasons in the same way that commitIndexBuild already does. See this comment for a repro. |
| Comments |
| Comment by Githook User [ 31/Jan/20 ] |
|
Author: {'name': 'Louis Williams', 'username': 'louiswilliams', 'email': 'louis.williams@mongodb.com'}Message: |
| Comment by William Schultz (Inactive) [ 31/Jan/20 ] |
|
I haven't seen the bug appear in any real BFs yet, so it's probably not very urgent, but I imagine it will turn up sooner or later as a BF. I suppose it could also be done as a follow up commit on |
| Comment by Louis Williams [ 31/Jan/20 ] |
|
william.schultz, let me know if this needs to be scheduled soon. |