[SERVER-85861] Stream processing instance out of memory when 6GB window is closed Created: 29/Jan/24 Updated: 29/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Normyle | Assignee: | Backlog - Atlas Streams |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Atlas Streams
|
| Operating System: | ALL |
| Participants: |
| Description |
|
In this PR, I added a smoketest that creates a 6GB window. Things work fine when the window is open, and the SP reports the expected stateSize. When the window is closed, the SP runs into "Stream processing instance out of memory". We should understand where this memory spike comes from, it doesn't seem like it should be happening. We can likely re-create this using jstests against a local engine build. |