[
https://issues.apache.org/jira/browse/HADOOP-6508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805349#action_12805349
]
Amareshwari Sriramadasu commented on HADOOP-6508:
-------------------------------------------------
Some simple experiments we have done:
1. We brought up 500 node cluster with CompositeContext containing Contexts C1
and C2. The metric for number of trackers is correct in C1( same number as in
web UI) and is wrong in C2.
2. We brought up 500 node cluster with CompositeContext containing Contexts C2
and C1 (Interchanged the order of contexts from the earlier). Then, the metric
for number of trackers is correct in C2( same number as in web UI) and is wrong
in C1.
Here, the code path, "in which the metric for number of trackers is
incremented", is JobTracker.addNewTracker() whenever a new tracker is added.
Since first context's value matches with the one on web UI. There is no bug in
JobTracker updating code. Also there is no bug in individual context
implementations, because it is always second context showing wrong values.
Thus, this leaves there is bug in metrics framework i.e. CompositeContext.
> Incorrect values for metrics with CompositeContext
> --------------------------------------------------
>
> Key: HADOOP-6508
> URL: https://issues.apache.org/jira/browse/HADOOP-6508
> Project: Hadoop Common
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.20.0
> Reporter: Amareshwari Sriramadasu
> Fix For: 0.22.0
>
>
> In our clusters, when we use CompositeContext with two contexts, second
> context gets wrong values.
> This problem is consistent on 500 (and above) node cluster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
