Q: A batch processing job is consuming all available CPU, starving other services on the same server. How do you lower its CPU priority without killing it?
Linux uses a nice value (ranging from -20 to +19) to influence CPU scheduling priority. Higher nice values mean lower priority (the process is "nicer" to others).
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 scheduling, nice/renice, cgroups.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Linux uses a nice value (ranging from -20 to +19) to influence CPU scheduling priority. Higher nice values mean lower priority (the process is "nicer" to others).
renice:renice +15 -psets the process to a low priority, allowing other processes to get CPU time first.- Starting with low priority:
nice -n 15 ./batch_job.shlaunches the process with reduced priority from the start.
Remediation & Permanent Safeguards
To reduce priority of a running process: For stricter enforcement, use cgroups: This limits the process to 25% of a single CPU core regardless of system load—a hard cap rather than a scheduling hint. The difference: nice is a *soft* priority hint that only matters under contention. Cgroups provide a *hard* resource limit that is enforced regardless of whether other processes need CPU.
systemd-run --scope --property=CPUQuota=25% ./batch_job.sh
- renice: renice +15 -p sets the process to a low priority, allowing other processes to get CPU ti...
- Starting with low priority: nice -n 15 ./batch_job.sh launches the process with reduced priority ...
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 batch processing consuming 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 batch processing consuming
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 batch processing consuming 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 batch processing consuming
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).