The article explains how to achieve a graceful termination of a Linux process by sending SIGTERM (kill -15), how the signal translates into a thread interrupt that causes sleep to throw an exception, and why the end‑flag still prints in a simple Spring Boot‑style example.
This article explains how to use the Linux kill command with SIGTERM, SIGQUIT, SIGKILL, and SIGSTOP signals to gracefully terminate, debug, force‑stop, or pause processes while minimizing data loss and providing practical command examples.
This article explains why a Kubernetes pod may remain in the Terminating state for up to 30 seconds, detailing the graceful shutdown process, the role of terminationGracePeriodSeconds and preStop hooks, and how to modify startup scripts to ensure prompt pod deletion.
Deleting a pod triggers endpoint removal, but various components like kube-proxy, CoreDNS, and ingress controllers may still route traffic until the endpoint fully propagates, so you must wait or use preStop hooks to delay deletion and handle SIGTERM gracefully within the configurable shutdown period.
During a Kubernetes deployment, the old pod is terminated while the new one starts, and by adding a preStop hook and properly configuring terminationGracePeriodSeconds, you can ensure graceful shutdown, propagate SIGTERM to all processes, avoid traffic loss, and handle signal forwarding for multi‑process containers.
The article explains the dangers of using kill -9 to terminate Java processes, illustrates how it can cause data loss in database operations, and provides several practical approaches—including SIGTERM, ConfigurableApplicationContext.close(), Spring Boot Actuator, and a custom Tomcat shutdown hook—to gracefully stop Spring Boot services while preserving data integrity.
This article explains why Docker containers may need around ten seconds to stop, covering missing init processes, unhandled SIGTERM signals, and practical Dockerfile adjustments such as using exec‑form ENTRYPOINT, adding signal traps, or employing a lightweight init like tini.
Graceful application shutdown prevents blocked requests, accidental data writes, and operation failures by releasing resources, closing database connections, and handling SIGTERM signals, and this article outlines a practical step-by-step process—including load balancer coordination and sample Node.js code—to ensure clean termination.
