hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5237) ClusterStatus incompatiblity issues with MR1
Date Fri, 24 May 2013 17:02:20 GMT

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

Zhijie Shen commented on MAPREDUCE-5237:
----------------------------------------

Hm... Though MR 1.x applications will not use INVALID explicitly, there's still the risk of
being broken. For example,

{code}
switch(clusterStatus.getJobTrackerState()) {
  case INITIALIZING:
    ...;
    break;
  case RUNNING:
    ...;
    break;
  default:
    throw new Exception("Unexpected State");
}
{code}

Thanks, Mayank! I'll modify the code accordingly.
                
> 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
>         Attachments: MAPREDUCE-5237.1.patch, MAPREDUCE-5237.2.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

Mime
View raw message