Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1124931345.1226104064237.JavaMail.jira@brutus>
Date: Fri, 7 Nov 2008 16:27:44 -0800 (PST)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4618) Move http server from FSNamesystem
 into NameNode.
In-Reply-To: <1459165064.1226096504189.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Shvachko updated HADOOP-4618:
----------------------------------------

    Status: Patch Available  (was: Open)

> Move http server from FSNamesystem into NameNode.
> -------------------------------------------------
>
>                 Key: HADOOP-4618
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4618
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.1.0
>            Reporter: Konstantin Shvachko
>            Assignee: Konstantin Shvachko
>             Fix For: 0.20.0
>
>         Attachments: MoveHttpServer.patch
>
>
> NameNode is responsible now for starting its RPC server. The (web UI) http server is started inside FSNamesystem class.
> I think it should be the NameNode's responsibility to deal with all issues intended for exposing information it holds to the outside world. This should include the RCP server as well as the http server.
> And FSNamesystem class should be a logical container of internal namespace data-structures and in general should not be accessed directly from the outside.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.