hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jothi Padmanabhan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-881) Jobtracker continues even if History initialization fails
Date Thu, 10 Sep 2009 16:25:57 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753685#action_12753685
] 

Jothi Padmanabhan commented on MAPREDUCE-881:
---------------------------------------------

In MAPREDUCE-157, we do just that -- let JT fail if there is a problem with history initialization.
We could close this after that gets in

> 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.


Mime
View raw message