[
https://issues.apache.org/jira/browse/MAPREDUCE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537825#comment-13537825
]
Hudson commented on MAPREDUCE-4845:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #470 (See
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/470/])
MAPREDUCE-4845. ClusterStatus.getMaxMemory() and getUsedMemory() exist in
MR1 but not MR2 (Sandy Ryza via tgraves) (Revision 1424729)
Result = UNSTABLE
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1424729
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/ClusterStatus.java
> ClusterStatus.getMaxMemory() and getUsedMemory() exist in MR1 but not MR2
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-4845
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4845
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Affects Versions: 1.1.1, 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 1.2.0, 2.0.3-alpha, 0.23.6
>
> Attachments: MAPREDUCE-4845-branch-1.patch, MAPREDUCE-4845.patch,
> MAPREDUCE-4845.patch
>
>
> For backwards compatibility, these methods should exist in both MR1 and MR2.
> Confusingly, these methods return the max memory and used memory of the
> jobtracker, not the entire cluster.
> I'd propose to add them to MR2 and return -1, and deprecate them in both MR1
> and MR2. Alternatively, I could add plumbing to get the resource manager
> memory stats.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
