You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2015/05/15 21:51:59 UTC
[jira] [Updated] (MESOS-2741) Exposing Resources along with
ResourceStatistics from resource monitor
[ https://issues.apache.org/jira/browse/MESOS-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jie Yu updated MESOS-2741:
--------------------------
Description:
Right now, the resource monitor returns a Usage which contains ContainerId, ExecutorInfo and ResourceStatistics. In order for resource estimator/qos controller to calculate usage slack, or tell if a container is using revokable resources or not, we need to expose the Resources that are currently assigned to the container.
This requires us the change the containerizer interface to get the Resources as well while calling 'usage()'.
was:Right now, the resource monitor returns a Usage which contains ContainerId, ExecutorInfo and ResourceStatistics. In order for resource estimator/qos controller to calculate usage slack, or tell if a container is using revokable resources or not, we need to expose the Resources that are currently assigned to the container.
> Exposing Resources along with ResourceStatistics from resource monitor
> ----------------------------------------------------------------------
>
> Key: MESOS-2741
> URL: https://issues.apache.org/jira/browse/MESOS-2741
> Project: Mesos
> Issue Type: Bug
> Reporter: Jie Yu
> Labels: twitter
>
> Right now, the resource monitor returns a Usage which contains ContainerId, ExecutorInfo and ResourceStatistics. In order for resource estimator/qos controller to calculate usage slack, or tell if a container is using revokable resources or not, we need to expose the Resources that are currently assigned to the container.
> This requires us the change the containerizer interface to get the Resources as well while calling 'usage()'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)