[ 
https://issues.apache.org/jira/browse/YARN-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763763#comment-15763763
 ] 

Chuan Jin edited comment on YARN-2984 at 12/20/16 9:37 AM:
-----------------------------------------------------------

I upgrade my cluster to this version from 2.5.2 , but soon realize that my 
ganglia servers have run out of disk space. The container metrics data is huge 
especially in large clusters,  and less valuable than the service metrics  in 
most time. So why not change the default value of  
yarn.nodemanager.container-metrics.enable to false,  that may be more 
reasonable in a production environment. Thanks.



was (Author: king0719):
I upgrade my cluster to this version from 2.5.2 , but soon realize that my 
ganglia servers have run out of disk space. The container metrics data is huge 
especially in large clusters,  and less valuable than the service metrics  in 
most time. So why not change the default value of  
yarn.nodemanager.container-metrics.enable to false,  that may be more 
reasonable in a production environment.


> Metrics for container's actual memory usage
> -------------------------------------------
>
>                 Key: YARN-2984
>                 URL: https://issues.apache.org/jira/browse/YARN-2984
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.6.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>             Fix For: 2.7.0
>
>         Attachments: yarn-2984-1.patch, yarn-2984-2.patch, yarn-2984-3.patch, 
> yarn-2984-prelim.patch
>
>
> It would be nice to capture resource usage per container, for a variety of 
> reasons. This JIRA is to track memory usage. 
> YARN-2965 tracks the resource usage on the node, and the two implementations 
> should reuse code as much as possible. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to