[
https://issues.apache.org/jira/browse/HADOOP-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanping Wang updated HADOOP-7331:
---------------------------------
Attachment: HDFS-7331.2.patch
Thanks for the comment! I agree that we need a more complex mechanism in order
for hadoop-daemon.sh process to really know that daemons are not able to start
due to various problems that may happen. Suppose now we want to restrict our
problem set to deal with the issues like invalid config or unable to bind
address in which cases the daemon should die rather quickly after starting.
What about having a simple solution for now: we put the process to sleep for a
few seconds before checking pid? (Made changes based the feedback.)
> Makes hadoop-daemon.sh to return 1 if daemon processes did not get started
> --------------------------------------------------------------------------
>
> Key: HADOOP-7331
> URL: https://issues.apache.org/jira/browse/HADOOP-7331
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 0.23.0
> Reporter: Tanping Wang
> Assignee: Tanping Wang
> Priority: Trivial
> Fix For: 0.23.0
>
> Attachments: HADOOP-7331.patch, HDFS-7331.2.patch
>
>
> Makes hadoop-daemon.sh to return 1 if daemon processes did not get started.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
