[SERVER-54212] Interrupted canonicalization can cause crash Created: 02/Feb/21 Updated: 02/Feb/21 Resolved: 02/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 4.9.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Joel Redman (Inactive) | Assignee: | Joel Redman (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Either add a failpoint to canonicalize, or interrupt the following query: db.coll.distinct( "a", { "b" : 1} ) |
||||||||
| Sprint: | Query 2021-02-08 | ||||||||
| Participants: | |||||||||
| Description |
|
During a distinct without projects, it's possible that an interruption will cause the server to crash. This is due to a failure to check the return code of canonicalize in getExecutorWithoutProjection. |