You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2012/10/16 22:59:04 UTC
[jira] [Commented] (MAPREDUCE-4596) Split StateMachine state from
states seen by MRClientProtocol (for Job, Task, TaskAttempt)
[ https://issues.apache.org/jira/browse/MAPREDUCE-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477339#comment-13477339 ]
Vinod Kumar Vavilapalli commented on MAPREDUCE-4596:
----------------------------------------------------
Looks good overall.
One comment( that doesn't need a response). MRApps.TaskAttemptStateUI is almost same as external state now, but we can leave it as is because we primarily need it for the mapping.
+1. Will commit it once Jenkins blesses the patch.
> Split StateMachine state from states seen by MRClientProtocol (for Job, Task, TaskAttempt)
> ------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4596
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4596
> Project: Hadoop Map/Reduce
> Issue Type: Task
> Components: applicationmaster, mrv2
> Affects Versions: 0.23.0
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: MR4596_2.txt, MR4596_3.txt, MR4596-branch23_1.txt, MR4596.txt
>
>
> State machine states are currently exposed via MRClienProtocol. This makes it tough to modify the AM state machines, or have an alternate AM with different state machines (MR-3902) without the changes being visible in MRClientProtocol (MRv2 equivalent of ClientProtocol).
--
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