[
https://issues.apache.org/jira/browse/HDFS-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229499#comment-13229499
]
Avik Dey commented on HDFS-1623:
--------------------------------
Suresh - Thanks for sharing the notes from this discussion on HDFS Namenode
HA.
Good to see that we are embracing both the IP based NN failover solution as
well as a replacement for the NFS based solution through the BN
implementation. From this thread as well as reviewing the jiras most of the
current thinking for failover seems to be around a single SBN. Keeping in
mind typical goals for HA in an enterprise environment and redundancy
requirements around it, I would like to suggest that the community consider
at least a dual SBN solution.
Ideally off course the HA solution would allow for N (N=0 to x) number of
SBNs driven by the HA needs of the specific deployment, however that would
possibly require a additional design / implementation for leader election
mechanism or some predetermined and configured ordering of SBNs.
Implementing such a generic N SBN solution would probably add some design
complexity and push out the release of this HA solution further in to the
future.
However, the dual SBN solution should be relatively less involved and
easier to implement leveraging the same approach of VIPs and HDFS-3077 +
HDFS-3092 while providing significantly higher redundancy in a HA failover
scenario.
Best Regards.
Avik
On Wed, Mar 14, 2012 at 9:40 AM, Suresh Srinivas (Commented) (JIRA) <
> High Availability Framework for HDFS NN
> ---------------------------------------
>
> Key: HDFS-1623
> URL: https://issues.apache.org/jira/browse/HDFS-1623
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Sanjay Radia
> Fix For: 0.24.0, 0.23.3
>
> Attachments: HA-tests.pdf, HDFS-1623.rel23.patch,
> HDFS-1623.trunk.patch, HDFS-High-Availability.pdf, NameNode HA_v2.pdf,
> NameNode HA_v2_1.pdf, Namenode HA Framework.pdf, dfsio-results.tsv,
> ha-testplan.pdf, ha-testplan.tex
>
>
--
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
