Q: Explain the difference between SIGTERM and SIGKILL. Why must applications handle SIGTERM gracefully before deployment, and what happens during Kubernetes pod termination?
SIGTERM (signal 15): A "polite request" to terminate. The process can catch it, perform cleanup (flush buffers, close connections), and exit cleanly.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "During an on-call shift, our alerts triggered when a critical Linux production server exhibited this behavior. The interviewer is testing: Process signals, graceful shutdown, orchestration lifecycle.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
SIGTERM (signal 15): A "polite request" to terminate. The process can catch it, perform cleanup (flush buffers, close connections), and exit cleanly.
- When scaling down or rolling out updates, the orchestrator sends SIGTERM to the application (e.g., 30-second grace period).
- The application must catch SIGTERM and gracefully shutdown:
- During shutdown: close client connections, finish in-flight requests, flush logs, release resources.
- If the process doesn't exit cleanly within the grace period, Kubernetes sends SIGKILL, forcefully terminating it (potential data loss or corrupted state).
Remediation & Permanent Safeguards
SIGKILL (signal 9): A "forced kill" that cannot be caught or ignored. The kernel immediately terminates the process, potentially leaving corrupted state. In production deployments (especially Kubernetes): Applications that don't handle SIGTERM risk: Example: A web server catching SIGTERM stops accepting *new* connections but finishes serving existing requests before exiting.
trap 'graceful_shutdown' SIGTERM
- Lost in-flight requests
- Corrupted database transactions
- Connection pool exhaustion (clients hang waiting for responses)
- When scaling down or rolling out updates, the orchestrator sends SIGTERM to the application (e.g....
- The application must catch SIGTERM and gracefully shutdown:
- During shutdown: close client connections, finish in-flight requests, flush logs, release resources.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring Explain difference SIGTERM SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring Explain difference SIGTERM
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring Explain difference SIGTERM Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring Explain difference SIGTERM
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).