在OOM之后，我如何检测导致它的吊舱? [英] After an OOM how can I detect the pod that caused it?

问题描述

我在群集上运行某些Pod时遇到一些问题，我想知道在引发异常后检测哪个Pod(和rc)在我的节点上导致OOM的方法.我无法访问该节点以检查日志，并且kubectl describe node并没有给我太多有关此的信息.

I had some issues running some pods on a cluster, I want to know the way to detect which pod (and rc) is causing OOM on my nodes after the exception is thrown. I cannot access the node to check logs and kubectl describe node doesn't give me much information about this.

谢谢:)

推荐答案

我发现跟踪正在发生的事情的唯一方法是等待在Web UI上抛出OOM之后

The only way I found to track what is happening is waiting before an OOM is thrown on the web UI link and tracking the pod's memory used (I had a node with 1.75 GB and a pod that was consuming 1.3GB). I tried to see the memory allocation with kubectl describe node [nodename] but I couldn't.

这篇关于在OOM之后，我如何检测导致它的吊舱?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！