[SERVER-36748] memory.js should verify that the ooming $where actually ooms Created: 17/Aug/18 Updated: 29/Oct/23 Resolved: 15/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Gabriel Russell (Inactive) |
| 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: | Service Arch 2018-11-19, Service Arch 2018-12-03, Service Arch 2018-12-17, Service Arch 2018-12-31, Service Arch 2019-01-14, Service Arch 2019-01-28, Service Arch 2019-02-11, Service Arch 2019-02-25, Dev Tools 2019-04-08, Service Arch 2019-03-11, Dev Tools 2019-05-06, Dev Tools 2019-05-20, Dev Tools 2019-04-22 | ||||
| Participants: | |||||
| Linked BF Score: | 13 | ||||
| Description |
|
memory.js forces an oom in a $where which can actually fail with interrupted. That can cause the next operation to oom when it uses the previous scope. Forcing a gc before every query isn't reasonable, and the test pushes right up to system limits, so there probably isn't a good argument for fixing anything outside the test. But it would at least be good to know that the $where timed out, rather than ooming |
| Comments |
| Comment by Githook User [ 15/May/19 ] |
|
Author: {'email': 'gabriel.russell@mongodb.com', 'name': 'Gabriel Russell', 'username': 'gabrielrussell'}Message: |