You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Klaus Ma (JIRA)" <ji...@apache.org> on 2015/09/10 03:42:45 UTC
[jira] [Updated] (MESOS-2875) Add containerId to ResourceUsage to
enable QoS controller to target a container
[ https://issues.apache.org/jira/browse/MESOS-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Klaus Ma updated MESOS-2875:
----------------------------
Component/s: oversubscription
> 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
> Components: oversubscription
> Reporter: Niklas Quarfot Nielsen
> Assignee: Klaus Ma
> Labels: race-condition, slave
>
> 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)