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] Created: (HADOOP-4618) Move http server from FSNamesystem into NameNode.
Date Fri, 07 Nov 2008 22:21:44 GMT
Move http server from FSNamesystem into NameNode.
-------------------------------------------------

                 Key: HADOOP-4618
                 URL: https://issues.apache.org/jira/browse/HADOOP-4618
             Project: Hadoop Core
          Issue Type: Bug
    Affects Versions: 0.1.0
            Reporter: Konstantin Shvachko
            Assignee: Konstantin Shvachko
             Fix For: 0.20.0


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.
I came to this conclusion trying to implement a standby node. SNN and NN should be represented
by the same class, since one can turn into another and vice versa during their life time.
I realized that with current implementation the node startup logic will be spread between
two classes ({{NameNode}} and {{FSNamesystem}}), which is inconvenient, complex, and error
prone.

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