Difference between revisions of "OOMKilling"
Jump to navigation
Jump to search
| (2 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
== Related == | == Related == | ||
* <code>[[kubectl get events]]</code> | * <code>[[kubectl get events]]</code> | ||
| + | * <code>[[OOMKilled]]</code> | ||
== See also == | == See also == | ||
* {{kubectl get events}} | * {{kubectl get events}} | ||
| + | * {{Kubernetes nodes events}} | ||
[[Category:Kubectl]] | [[Category:Kubectl]] | ||
Latest revision as of 11:14, 30 December 2022
27m Warning OOMKilling node/gke-you-pool4 Memory cgroup out of memory: Killed process 2768158 (python) total-vm:5613088kB, anon-rss:3051580kB, file-rss:65400kB, shmem-rss:0kB, UID:0 pgtables:7028kB oom_score_adj:997
Related[edit]
See also[edit]
kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed- Kubernetes node events: Kubernetes node events,
NodeNotSchedulable,NodeAllocatableEnforced,NodeHasNoDiskPressure, DiskPressure, NodeHasSufficientMemory,NodeHasSufficientPID,RegisteredNode,InvalidDiskCapacity,Starting,NodeReady,RemovingNode
Advertising:
