[ 
https://issues.apache.org/jira/browse/MESOS-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Niklas Quarfot Nielsen updated MESOS-2653:
------------------------------------------
    Description: 
Slave might want to kill revocable tasks based on correction events from the 
QoS controller.

The QoS controller communicates corrections through a stream (or 
process::Queue) to the slave which corrections it needs to carry out, in order 
to mitigate interference with production tasks.

The correction is communicated through a message:
[code]
message QoSCorrection {
     enum CorrectionType {
         KillExecutor = 1
         // KillTask = 2
         // Resize, throttle task
     }
optional string reason = X;
optional ExecutorID executor_id = X;
// optional TaskID task_id = X;
}
[/code]

And the slave will setup a handler to process these events. Initially, only 
executor termination is supported and cause the slave to issue 
'containerizer->destroy()'.

  was:Slave might want to kill revocable tasks based on correction events from 
the QoS controller.


> Slave should act on correction events from QoS controller
> ---------------------------------------------------------
>
>                 Key: MESOS-2653
>                 URL: https://issues.apache.org/jira/browse/MESOS-2653
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Vinod Kone
>              Labels: mesosphere
>
> Slave might want to kill revocable tasks based on correction events from the 
> QoS controller.
> The QoS controller communicates corrections through a stream (or 
> process::Queue) to the slave which corrections it needs to carry out, in 
> order to mitigate interference with production tasks.
> The correction is communicated through a message:
> [code]
> message QoSCorrection {
>      enum CorrectionType {
>          KillExecutor = 1
>          // KillTask = 2
>          // Resize, throttle task
>      }
> optional string reason = X;
> optional ExecutorID executor_id = X;
> // optional TaskID task_id = X;
> }
> [/code]
> And the slave will setup a handler to process these events. Initially, only 
> executor termination is supported and cause the slave to issue 
> 'containerizer->destroy()'.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to