[
https://issues.apache.org/jira/browse/MAPREDUCE-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-5441:
-----------------------------------------------
Status: Open (was: Patch Available)
The patch looks fine.
Please leave a comment as to why we are returning RUNNING.
Our code style is to use parenthesis all the time (changes in JobImpl).
We should also have a more direct test-case. You can use MRApp for this.
- Start MRApp with a custom RMContainerAllocator.
- Throw a token exception when MRApp heartbeats.
- Check the end state by inspecting Job's state.
> JobClient exit whenever RM issue Reboot command to 1st attempt App Master.
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-5441
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5441
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster, client
> Affects Versions: 2.0.5-alpha, 2.1.0-beta, 2.1.1-beta
> Reporter: Rohith Sharma K S
> Assignee: Jian He
> Attachments: MAPREDUCE-5441.1.patch, MAPREDUCE-5441.2.patch,
> MAPREDUCE-5441.patch
>
>
> When RM issue Reboot command to app master, app master shutdown gracefully.
> All the history event are writtent to hdfs with job status set as ERROR.
> Jobclient get job state as ERROR and exit.
> But RM launches 2nd attempt app master where no client are there to get job
> status.In RM UI, job status is displayed as SUCCESS but for client Job is
> Failed.
--
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
