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 "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2013/08/20 05:15:52 UTC
[jira] [Commented] (MAPREDUCE-5401) Succeeded Job details displayed
as Error In JobHistoryServer UI when RM issues Reboot to 1st app master.
[ https://issues.apache.org/jira/browse/MAPREDUCE-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744648#comment-13744648 ]
Rohith Sharma K S commented on MAPREDUCE-5401:
----------------------------------------------
I think this issue we can duplicate as MAPREDUCE-5466. Both issues expectations are same.
> Succeeded Job details displayed as Error In JobHistoryServer UI when RM issues Reboot to 1st app master.
> ---------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5401
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5401
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.0.5-alpha
> Environment: Hadoop-2.0.5-alpha cluster
> Reporter: Rohith Sharma K S
>
> RM issues Reboot to 1st attempt app master and lauches 2nd attempt app master in available NodeManager.
> 1st attempt app master shutdown gracefully , not deleting staging directory which is handled in MAPREDUCE-5086. But problem is 1st attempt app master creates jhist(Error),summary and config file.
> 2nd attempt app master also create jhist(succeeded) , summary and config file.
> While moving summary file, since file is already exist of 1st attempt summary file, 2nd attempt summary remain as summary_tmp
--
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