hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4724) TaskTracker, DataNode, and SecondaryNameNode should timeout on waiting for its server to be up
Date Tue, 25 Nov 2008 19:47:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650701#action_12650701
] 

Tsz Wo (Nicholas), SZE commented on HADOOP-4724:
------------------------------------------------

+1 for this change 

Currently, waitForProxy(...) waits forever if there are ConnectException. It seems not right
since if the server in the other side is down, the client cannot detect it but keep waiting.

> TaskTracker, DataNode, and SecondaryNameNode should timeout on waiting for its server
to be up
> ----------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4724
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4724
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Hairong Kuang
>             Fix For: 0.20.0
>
>
> TaskTracker, DataNode, and SecondaryNameNode currently wait forever if its server is
not up. They should be designed to take a configuration parameter that tells them when to
give up, and a default value of many minutes/hours or more to deal with basic choreography
issues in a cluster. Test clusters can be set up to fail sooner rather than later.

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