[
https://issues.apache.org/jira/browse/HADOOP-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849985#comment-13849985
]
Yang He commented on HADOOP-10161:
----------------------------------
The patch will back the old versions and just extend the feature, so I think it
will not harm current users because the default global value will remain what
it is(the default value of dmax is not changed,their old unused metrics stay in
memey forever). I make the change by two ways: first we can set global default
value of dmax for all metrics in hadoop.properties(also can unset), and in the
other way we can set default dmax value for special Context such as 'dfs' in
which way we can set the dmax for all metrics for 'dfs' context and not impact
other metrics like 'jvm' etc. Can we accept this?
> Add a method to change the default value of dmax in hadoop.properties
> ---------------------------------------------------------------------
>
> Key: HADOOP-10161
> URL: https://issues.apache.org/jira/browse/HADOOP-10161
> Project: Hadoop Common
> Issue Type: Improvement
> Components: metrics
> Affects Versions: 2.2.0
> Reporter: Yang He
> Attachments: HADOOP-10161_0_20131211.patch,
> hadoop-metrics.properties, hadoop-metrics2.properties
>
>
> The property of dmax in ganglia is a configurable time to rotate metrics.
> Therefore, no more value of the metric will be emit to the gmond, after
> 'dmax' seconds, then gmond will destroy the metric in memory. In Hadoop
> metrics framework, the default value of 'dmax' is 0. It means the gmond will
> never destroy the metric although the metric is disappeared. The gmetad
> daemon also does not delete the rrdtool file forever.
> We need to add a method to configure the default value of dmax for all
> metrics in hadoop.properties.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
