BestHub
Sign in
Tagged articles
7 articles
Page 1 of 1
Java Backend Technology
Java Backend Technology
Oct 14, 2024 · Cloud Native

Why ExitOnOutOfMemoryError Beats HeapDumpOnOutOfMemoryError in Containerized Java Apps

This article explains why, in containerized Java applications, the JVM flag -XX:+ExitOnOutOfMemoryError is generally preferred over -XX:+HeapDumpOnOutOfMemoryError, detailing the trade‑offs, operational benefits, and how Kubernetes probes and monitoring can ensure fast failure, rapid recovery, and user‑transparent service continuity.

ContainerJVMJava
0 likes · 11 min read
Why ExitOnOutOfMemoryError Beats HeapDumpOnOutOfMemoryError in Containerized Java Apps
Open Source Linux
Open Source Linux
Jan 28, 2023 · Cloud Native

Mastering Kubernetes Probes: Startup, Liveness, and Readiness Explained

This article explains why Kubernetes uses Startup, Liveness, and Readiness probes, describes common Pod states and restart policies, compares the probes, details their configuration fields, and provides practical YAML examples for each probe type to ensure reliable container health monitoring.

KubernetesLivenessProbePod
0 likes · 17 min read
Mastering Kubernetes Probes: Startup, Liveness, and Readiness Explained
Ops Development Stories
Ops Development Stories
Jun 1, 2021 · Cloud Native

Why Do Readiness Probe Failures Show “OCI runtime exec failed: EOF” in Kubernetes?

A Kubernetes pod reported readiness probe warnings with an OCI runtime exec failure, which was traced through kubelet, Docker, dockershim, containerd, and runc, ultimately caused by a race condition with cpu‑manager updating the container state file, and resolved by disabling cpu‑manager or upgrading runc.

CPU ManagerKubernetesOCI runtime
0 likes · 14 min read
Why Do Readiness Probe Failures Show “OCI runtime exec failed: EOF” in Kubernetes?
Cloud Native Technology Community
Cloud Native Technology Community
Dec 16, 2019 · Cloud Native

Why Does Rolling Update Trigger “No Route to Host” in Kubernetes?

A Kubernetes user reported intermittent “No route to host” errors during Deployment rolling updates, and this article analyzes common connection‑related errors, explains how IPVS weight handling and source‑port reuse cause the issue, and provides mitigation strategies such as preStop hooks, readiness probes, scaling, and anti‑affinity.

IPVSKubernetesRolling Update
0 likes · 15 min read
Why Does Rolling Update Trigger “No Route to Host” in Kubernetes?