Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 28 Aug 2012 08:55:07 +1100 (NCT)
From: "Siddharth Seth (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <584148599.3623.1346104508014.JavaMail.jiratomcat@arcas>
In-Reply-To: <128333857.3575.1346103788069.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (MAPREDUCE-4596) Split StateMachine state from
 states seen by MRClientProtocol (for Job, Task, TaskAttempt)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Seth updated MAPREDUCE-4596:
--------------------------------------

    Status: Patch Available  (was: Open)
    
> 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.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