hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2354) Generalize the HAServiceProtocol interface
Date Tue, 01 Nov 2011 00:09:33 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140712#comment-13140712
] 

Suresh Srinivas commented on HDFS-2354:
---------------------------------------

HDFS-1623, since I am one of the authors of the original document, I do think the current
approach cater to the issues you are talking about.
I believe you can do every thing you want to do, keeping a simple interface to namenode and
building other logic into the entity that interfaces with it, irrespective whether that entity
is outside NN process or inside.
                
> Generalize the HAServiceProtocol interface
> ------------------------------------------
>
>                 Key: HDFS-2354
>                 URL: https://issues.apache.org/jira/browse/HDFS-2354
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>            Reporter: Justin Joseph
>            Assignee: Justin Joseph
>         Attachments: HAService_fw_Class_Diagram.JPG, HDFS-2354.1.patch, HDFS-2354.patch,
Namenode HA using Backup Namenode as Hot Standby.pdf
>
>
> This JIRA intends to revisit the patches committed for HADOOP-7455 and HDFS-1974 &
to provide more generic interfaces which allows alternative HA implementations to co-exist
complying with HAServiceProtocol.
> Some of the considerations are
> 1) Support life cycle methods (start*() and stop() APIs) in HAServiceProtocol
> 2) Support custom states in HAServiceProtocol
> 3) As per the patch submitted for HDFS-1974, Namenode implements HAService interface.
This needs to be reconsidered.
> I will elaborate on these points, in the form of comments below.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message