[
https://issues.apache.org/jira/browse/AMBARI-12860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122135#comment-15122135
]
Aravindan Vijayan commented on AMBARI-12860:
--------------------------------------------
[~robinlin]
This is more like a Yarn issue. Ambari metrics service uses Yarn APIs to get
the metrics.
Removing ambari-metrics label.
> Ambari in Docker Containers
> ---------------------------
>
> Key: AMBARI-12860
> URL: https://issues.apache.org/jira/browse/AMBARI-12860
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 2.1.0, trunk
> Environment: Openstack, nova-docker driver, Docker container on
> bare-metal machine
> Reporter: robinlin
>
> Hi
> I try the Ambari 2.1 and HDP 2.3 on the Docker Containers which is
> provisioned by Openstack. And the containers were provisioned on bare-metal
> machines.
> But after the stack was ready, I saw few problems
> 1) Metrics on utilized CPU and Memory are from physical host not the Docker
> Containers.
> 2) The values of properties
> {noformat}yarn.nodemanager.resource.memory-mb{noformat}
> and {noformat}yarn.nodemanager.resource.vcpu-vcores{noformat}
> are calculated based on the CPU and Memory on physical machine, which may
> hosts many Docker containers.
> Is there any plan to make these right?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
