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] Updated: (HADOOP-4618) Move http server from FSNamesystem into NameNode.
Date Mon, 10 Nov 2008 22:39:44 GMT

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

Konstantin Shvachko updated HADOOP-4618:

    Attachment: MoveHttpServer.patch

Thanks for the comments.
- Good point Steve, I will mark this as an incompatible change. The right way would have been
to deprecate getNameNodeInfoPort(), but there is no way to implement the method in FSNamesystem
as the http server is not there anymore.
- Nicholas, I agree I should have left the "final" section in place.
- JavaDoc warning is related to HADOOP-4621.

In this version I restored the final section and deprecated FSNamesystem.getDFSNameNodeAddress()
in order to be able to remove it later.

> 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, MoveHttpServer.patch, 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.

View raw message