Set command to spawn with lower priority in GenericScript Run method#438
Set command to spawn with lower priority in GenericScript Run method#438neddp wants to merge 1 commit into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Waiting for a new bosh-utils tag. |
|
|
1e496ef to
9f2cb04
Compare
Lifecycle scripts (drain, pre-start, post-start, post-deploy, etc.) are executed by the agent and inherit its scheduling priority. When a script is CPU-intensive (e.g. cloning large amounts of data from a database cluster), it can starve the agent's own event loop, causing the director to time out with an agent-unreachable error - even though the agent is technically alive and the script is making progress. The deployment then fails and the script has to run from scratch.
The stemcell already runs the agent at nice -15 (see bosh-linux-stemcell-builder@00054bd) to give it priority over BOSH-managed jobs (nice 0). However, lifecycle scripts spawned by the agent inherit that -15 priority, defeating the purpose.
This PR sets
SpawnWithLowerPriority = trueon theCommandstruct for all lifecycle scripts, so they run at a lower priority than the agent itself:BelowNormal.The priority logic itself lives entirely in bosh-utils (#142), which adds the
SpawnWithLowerPriorityfield toboshsys.Commandwith platform-specific priority logic inlined directly (no external dependency, as suggested by @rkoster).References