[
https://issues.apache.org/jira/browse/MESOS-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735862#comment-14735862
]
Niklas Quarfot Nielsen commented on MESOS-2875:
-----------------------------------------------
1) Framework launches task X for executor Y
2) QoS controller decides that Y should be killed due to interference
3) Executor Y stops naturally
4) Framework starts a new task X' for executor Y
5) QoS controller sends correction for executor Y
> Add containerId to ResourceUsage to enable QoS controller to target a
> container
> -------------------------------------------------------------------------------
>
> Key: MESOS-2875
> URL: https://issues.apache.org/jira/browse/MESOS-2875
> Project: Mesos
> Issue Type: Improvement
> Reporter: Niklas Quarfot Nielsen
>
> We should ensure that we are addressing the _container_ which the QoS
> controller intended to kill. Without this check, we may run into a scenario
> where the executor has terminated and one with the same id has started in the
> interim i.e. running in a different container than the one the QoS controller
> targeted.
> This most likely requires us to add containerId to the ResourceUsage message
> and encode the containerID in the QoS Correction message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
