Ticket #2536: make upper bound on time spent in Preempting/Vacate explicit

For adding support for draining partitionable slots (#2330), it is desired to make the upper bound on time spent in Preempting/Vacate explicit.

Currently, the boolean KILL expression is used to terminate the Preempting/Vacating state. This makes it awkward to compute how long it could take to drain a slot, because the upper bound on time, if any, is embedded in the boolean expression. Also, there is no standard way for the job to express its requirements or preferences.

The following is proposed:

[Add remarks]



Type: enhance           Last Change: 2011-Oct-17 19:03
Status: resolved          Created: 2011-Oct-10 15:46
Fixed Version: v070703           Broken Version: v070703 
Priority:          Subsystem:  
Assigned To: danb           Derived From: #2330
Creator: danb  Rust:  
Customer Group: cms  Visibility: public 
Notify: tstclair@redhat.com  Due Date: 20111014 

Derived Tickets:

#3470   Allow old signal escalation semantics and to use remove_killI_sig

Related Check-ins:

2011-Oct-27 09:37   Check-in [28006]: lots of little edits to try to make descriptions of the new MachineMaxVacateTime, JobMaxVacateTime, want_graceful_removal, and friends even more clear. ===GT=== #2536 (By Karen Miller )
2011-Oct-17 19:00   Check-in [27872]: Documented MachineMaxVacateTime and JobMaxVacateTime. #2536 (By Dan Bradley )
2011-Oct-17 19:00   Check-in [27873]: Documented want_graceful_removal. #2536 (By Dan Bradley )
2011-Oct-17 19:00   Check-in [27871]: Added MachineMaxVacateTime and JobMaxVacateTime and WantGracefulRemoval. #2536 (parent ticket #2330)  [...] (By Dan Bradley )