[
https://issues.apache.org/jira/browse/HDFS-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975657#action_12975657
]
dhruba borthakur commented on HDFS-1064:
----------------------------------------
hi Stack, as you rightly pointed out, there are two issues at play here.
Case1. where to store the namenode transaction log?
Case2. how to make the active namenode transfer control to a standby namenode
and how long does this failover process take?
In my view, these two issues are not tied up with one another.One can use NFS,
DRBD or even newer things like zookeeper/bookkeeper for storing the transaction
logs in Case1.
For Case2, we still have to work out the details. Sanjay's proposal seems to
say that we should attempt to address Case2 first. A design for Case2 should
work irrespective of the type of storage we chose in Case1. In fact, getting
the right design for Case2 is the more challenging part of implementing a fast
failover.
> NN Availability - umbrella Jira
> -------------------------------
>
> Key: HDFS-1064
> URL: https://issues.apache.org/jira/browse/HDFS-1064
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Sanjay Radia
>
> This is an umbrella jira for discussing availability of the HDFS NN and
> providing references to other Jiras that improve its availability. This
> includes, but is not limited to, automatic failover.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
