[
https://issues.apache.org/jira/browse/HDFS-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109730#comment-13109730
]
Justin Joseph commented on HDFS-2354:
-------------------------------------
Other considerations are
1) There had been lot of debate in HADOOP-7455 on supporting Neutral State.
Even now, there is lot of apprehension over how neutral state can be an
alternative to various fencing techniques. I don’t want to use this JIRA for
discussing neutral state again; we can do the discussion in a separate JIRA.
In this JIRA, I just want to highlight "neutral state" as an example use case
for supporting custom states in HAServiceProtocol interface.
2) As per the patch submitted for HDFS-1974, Namenode implements HAService
interface. For sure, there will be multiple implementations for HAService
interface. So it is better to reconsider this relationship introduced in
HDFS-1974.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
