[
https://issues.apache.org/jira/browse/MAPREDUCE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-1683:
-------------------------------------
Status: Resolved (was: Patch Available)
Release Note: Removes JNI calls to get jvm current/max heap usage in
ClusterStatus. Any instances of ClusterStatus serialized in a prior version
will not be correctly deserialized using the updated class. (was: Removes JNI
calls to get jvm current/max heap usage in ClusterStatus.)
Fix Version/s: (was: 0.21.0)
Resolution: Fixed
Both {{TestChild}} and {{TestPipes}} pass on my machine; neither should be
affected by this patch.
+1
I committed this. Thanks, Luke and Arun!
> 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
> Fix For: 0.22.0
>
> Attachments: M1683-1.patch, MAPREDUCE-1683_part2_yhadoop_20_10.patch,
> MAPREDUCE-1683_yhadoop_20_9.patch, MAPREDUCE-1683_yhadoop_20_S.patch,
> mr-1683-trunk-v1.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.
