[
https://issues.apache.org/jira/browse/MAPREDUCE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865660#action_12865660
]
Amareshwari Sriramadasu commented on MAPREDUCE-1683:
----------------------------------------------------
bq. Looks like JobClient.getClusterStatus(boolean detailed) won't behave as
expected, as there is no way to get jobtracker ClusterStatus with jobtracker
memory info from the new ClientProtocol due to MAPREDUCE-777.
I raised MAPREDUCE-1779 for this.
> Remove JNI calls from ClusterStatus cstr
> ----------------------------------------
>
> Key: MAPREDUCE-1683
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1683
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.2
> Reporter: Chris Douglas
> Assignee: Luke Lu
> Attachments: MAPREDUCE-1683_part2_yhadoop_20_10.patch,
> MAPREDUCE-1683_yhadoop_20_9.patch, MAPREDUCE-1683_yhadoop_20_S.patch
>
>
> The {{ClusterStatus}} constructor makes two JNI calls to the {{Runtime}} to
> fetch memory information. {{ClusterStatus}} instances are often created
> inside the {{JobTracker}} to obtain other, unrelated metrics (sometimes from
> schedulers' inner loops). Given that this information is related to the
> {{JobTracker}} process and not the cluster, the metrics are also available
> via {{JvmMetrics}}, and the jsps can gather this information for themselves:
> these fields can be removed from {{ClusterStatus}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
