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 2013/08/22 05:14:52 UTC
[jira] [Resolved] (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:all-tabpanel ]
Vinod Kumar Vavilapalli resolved MAPREDUCE-5401.
------------------------------------------------
Resolution: Duplicate
[~rohithsharma], you are right, closing this as duplicate.
Apologies for not noticing this earlier, we should've ideally closed the other one as duplicate. Tx for reporting.
> 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