Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <1921385.1164817942982.JavaMail.jira@brutus>
Date: Wed, 29 Nov 2006 08:32:22 -0800 (PST)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-430) http server should die if the
 Datanode fails.
In-Reply-To: <21253528.1154990113889.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-430?page=comments#action_12454357 ] 
            
Hadoop QA commented on HADOOP-430:
----------------------------------

+1, http://issues.apache.org/jira/secure/attachment/12345986/hadoop-430.patch applied and successfully tested against trunk revision 480611

> http server should die if the Datanode fails.
> ---------------------------------------------
>
>                 Key: HADOOP-430
>                 URL: http://issues.apache.org/jira/browse/HADOOP-430
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.5.0
>            Reporter: Konstantin Shvachko
>         Assigned To: Wendy Chien
>         Attachments: hadoop-430.patch
>
>
> HADOOP-375 changed the order in which a data node registers and starts its http server.
> Current version first starts the http server, then registers. As a result if the registration fails,
> which can happen e.g. if the datanode has illegal storage id (=does not belong to the cluster),
> the http server keeps running, which makes the data node seem running too.
> I think 2 things need to be done.
> 1) Datanode registration should precede the http server startup.
> 2) The http server should shutdown when the datanode fails (in general).
> I am attaching a patch for the first item.
> Does anybody know how the latter can be done in the version of jetty we are on now?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira