You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Amar Kamat (JIRA)" <ji...@apache.org> on 2009/09/11 06:24:57 UTC

[jira] Resolved: (MAPREDUCE-881) Jobtracker continues even if History initialization fails

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

Amar Kamat resolved MAPREDUCE-881.
----------------------------------

    Resolution: Duplicate

MAPREDUCE-157

> Jobtracker continues even if History initialization fails
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-881
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-881
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>            Reporter: Sharad Agarwal
>
> If there is some problem in the configuration, Job history initialization fails. JobHistory#init catches the exception and disable the history. This leads to job history not working as expected. However administrators won't notice that there is some problem in the config due to which history got disabled, unless they see the logs. Better approach would be to not catch the exception and let Jobtracker fail to come up if there is error in initialization.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.