hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1683) Remove JNI calls from ClusterStatus cstr
Date Sat, 10 Apr 2010 11:38:52 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855540#action_12855540
] 

Vinod K V commented on MAPREDUCE-1683:
--------------------------------------

+1 for leaving the memory vals in the detailed info.

Patch for 20 looks good too.

When working on the trunk patch, we should cleanup/remove all the useless constructors - constructors
are all package private so no harm in doing a cleanup here, I think.

> 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
>         Attachments: MAPREDUCE-1683_yhadoop_20_9.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message