[
https://issues.apache.org/jira/browse/HDFS-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081743#comment-13081743
]
Todd Lipcon commented on HDFS-1974:
-----------------------------------
bq. That is because currently NamenodeProtocols does not extend
JournalProtocol. When BackupNode code merges with Namenode, ActiveState
rejecting JOURNAL operations will become necessary.
Using Sanjay's new support for mix-in RPC implementations, we can continue to
keep JournalProtocol separate, and only "mix it in" when starting up as the BN.
> HA: Introduce active and standby states to the namenode
> -------------------------------------------------------
>
> Key: HDFS-1974
> URL: https://issues.apache.org/jira/browse/HDFS-1974
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Attachments: HDFS-1974.1.patch, HDFS-1974.2.patch, HDFS-1974.3.patch,
> HDFS-1974.4.patch, HDFS-1974.5.patch, HDFS-1974.patch
>
>
> Currently namenode supports active, secondary and backup roles. To support
> namenode high availability, active and standby states are needed. Note that
> this is different from the existing notion of namenode role, where a namenode
> cannot transition from one role to the other.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
