[
https://issues.apache.org/jira/browse/HADOOP-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650958#action_12650958
]
Steve Loughran commented on HADOOP-4724:
----------------------------------------
+1 for this. It's useful for development and easy to test (start these nodes
with nothing to bond to),
* What property names to use?
* What are reasonable defaults for production systems?
For minidfs we can run with a configuration that times out much faster; the
default timeout should be adequate for people setting up basic clusters on
real/virtual machines without any assumptions about NTP working :)
> 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.
