[
https://issues.apache.org/jira/browse/HDFS-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192009#comment-13192009
]
Justin Joseph commented on HDFS-2354:
-------------------------------------
Aaron, I agree with Suresh that HAServiceProtocol can be kept as a simple
interface to Namenode. To handle my use cases, I can build around this simple
interface. I am planning to work on this this after the HA framework is ready
for testing.
We can close this JIRA for now. If needed, I will raise another issue later. Is
that ok?
> Generalize the HAServiceProtocol interface
> ------------------------------------------
>
> Key: HDFS-2354
> URL: https://issues.apache.org/jira/browse/HDFS-2354
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, 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
