You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
now, per minute push of memory profiler is not enough for oom, especially for pod.
the k8s pod memory = rss + cache (not accurate.).
if a pod oom killed.
1, caused by rss memory. we could push a immediately memory profiler if memory rapidly increase to debug that.
2, caused by high cache memory.may be the dd-trace-go could provide some information on how to debug that.
use linux syscall mincore to get file cached memory.
2.1, check all file open by pid first, like log ~.
2.2, check all file in the pid file directory /root/pid/root.
the agent could push memory profiler immediately when rss rapidly increase.
like:
https://github.com/mosn/holmes
The text was updated successfully, but these errors were encountered: