-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
ALL
-
QE 2023-10-16, QE 2023-10-30
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
I tried re-enabling spill_to_disk after SERVER-77185 was done and backported, and even with the backports, I'm still seeing problems. Here are the problematic logs: https://parsley.mongodb.com/resmoke/e3675d4e2151a916de0ca82a4fb29a9c/all?bookmarks=0,4585,129264,173946&filters=000localhost%253A20753,000js_test_try,000j3%253Acl0%253As1%253Aprim&shareLine=129264
Essentially it seems that at some point when the test is running j3:cl0:s1:prim throws a QueryExceededMemoryLimitNoDiskUseAllowed, and then it never recovers or is reachable by the other nodes.