[ https://issues.apache.org/jira/browse/HADOOP-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604271#action_12604271
]
Ari Rabkin commented on HADOOP-3531:
------------------------------------
Inserting delays to fix synchro problems is a perilous course. Can we do something better,
like alternate between checking for an error code, and checking if the jetty interface came
up? Is there at least a principled way to pick the waiting period here?
> 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
>
> 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.
|