[SERVER-39237] Ensure $out with replaceCollection can clean up temp collection after interrupt Created: 28/Jan/19 Updated: 29/Oct/23 Resolved: 05/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Arun Banala |
| 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: | Query 2019-02-25, Query 2019-03-11 | ||||||||
| Participants: | |||||||||
| Description |
|
Right now it seems to be the case that an interrupt will flag the OperationContext in a way that makes it impossible to take any more locks. We need to take a lock one more time to drop the temp collection. First, we should verify whether this is actually an issue. If it is, we can take the same approach we took in MapReduce as part of |
| Comments |
| Comment by Githook User [ 05/Mar/19 ] |
|
Author: {'name': 'Arun Banala', 'username': 'banarun', 'email': 'arun.banala@mongodb.com'}Message: |
| Comment by Githook User [ 05/Mar/19 ] |
|
Author: {'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}Message: |