[
https://issues.apache.org/jira/browse/MESOS-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550825#comment-14550825
]
haosdent commented on MESOS-2741:
---------------------------------
And form implement this issue, how about change the interface in Container from
{code}
virtual process::Future<ResourceStatistics> usage(
const ContainerID& containerId) = 0;
{code}
to
{code}
virtual process::Future<ResourceMonitor::Usage> usage(
const ContainerID& containerId) = 0;
{code}
> 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: mesosphere, 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)
