hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4724) TaskTracker, DataNode, and SecondaryNameNode should timeout on waiting for its server to be up
Date Thu, 07 Jan 2010 11:11:08 GMT

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

Steve Loughran commented on HADOOP-4724:
----------------------------------------

With HADOOP-6435 fixed, this is now possible. 

There is also the problem that JobTracker now spins on startup waiting for the filesystem
to go live, that needs timeouts too. I'd like to move that code down to the worker thread,
but that's a separate issue

> 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 Common
>          Issue Type: Bug
>            Reporter: Hairong Kuang
>
> 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