hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4618) Move http server from FSNamesystem into NameNode.
Date Fri, 07 Nov 2008 23:57:44 GMT

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

Konstantin Shvachko commented on HADOOP-4618:
---------------------------------------------

One more change is that I moved field {{supportAppends}} from NameNode to {{FSNamesystem}}
where all such fields are used to be.

> 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.


Mime
View raw message