hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Daley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3531) Hod does not report job tracker failure on hod client side when job tracker fails to come up
Date Wed, 11 Jun 2008 23:08:44 GMT

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

Nigel Daley updated HADOOP-3531:
--------------------------------

    Fix Version/s: 0.18.0

Hemanth, this was marked a blocker, but had no release assigned.  Setting Fix Version to 0.18.
 Please correct that if I'm wrong.



> Hod does not  report job tracker failure on hod client side when job tracker fails to
come up
> ---------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3531
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3531
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/hod
>    Affects Versions: 0.18.0
>            Reporter: Karam Singh
>            Priority: Blocker
>             Fix For: 0.18.0
>
>
> Hod does not  report job tracker failure on hod client side when job tracker fails to
come up. 
> When max-master-failure > 1
> hod client does not properly show why job tracker failed to come up, while in case namenode
proper error message is displayed.
> Also in namenode failure ringmaster log contains information such as -: "Detected errors
(3) beyond allowed number of failures (2). Flagging error to client"
> while no such information is there in ringmaster log for job tracker failures

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