[
https://issues.apache.org/jira/browse/MAPREDUCE-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669273#comment-13669273
]
Hudson commented on MAPREDUCE-5237:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #1440 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1440/])
MAPREDUCE-5237. Add methods that were removed from ClusterStatus back into
2.x so as to be compatible with 1.x. Contributed by Zhijie Shen.
Incompatible as ClusterStatus.UNINITIALIZED_MEMORY_VALUE is a long now and so
breaks 0.23.x but it shouldn't be a big deal in reality. (Revision 1487175)
Result = SUCCESS
vinodkv :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1487175
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/ClusterStatus.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobTracker.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapred/TestClusterStatus.java
> ClusterStatus incompatiblity issues with MR1
> --------------------------------------------
>
> Key: MAPREDUCE-5237
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5237
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Fix For: 2.0.5-beta
>
> Attachments: MAPREDUCE-5237.1.patch, MAPREDUCE-5237.2.patch,
> MAPREDUCE-5237.3.patch
>
>
> The three functions are:
> Collection<String> getGraylistedTrackerNames()
> int getGraylistedTrackers()
> State getJobTrackerState()
> The're tracker related, such that they are no longer used in MR2. Maybe we
> should add them and throw UnsupportedOperationException?
> In addition, UNINITIALIZED_MEMORY_VALUE changes from long to int
--
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
