[
https://issues.apache.org/jira/browse/HDFS-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847653#action_12847653
]
ryan rawson commented on HDFS-1051:
-----------------------------------
Perhaps we could think of using Zab from Zookeeper to keep a cluster of
NewNameNodes in sync all the time? Instead of doing a failure detection and
failover and recovery, we could keep 2N+1 nodes always up to date. No recovery
would be necessary during node failover, rolling restarts and machine moves
would be doable (just like in ZK). This could reduce the deployment complexity
over some of the other options.
For metadata scalability in RAM, a possibility would be to leverage flash disk
in some capacity. Swap, mmap, explicit local files in flash would be
reasonably fast and could extend the serviceable life of the "1 machine holds
all metadata" architecture concept.
> Umbrella Jira for Scaling the HDFS Name Service
> -----------------------------------------------
>
> Key: HDFS-1051
> URL: https://issues.apache.org/jira/browse/HDFS-1051
> Project: Hadoop HDFS
> Issue Type: New Feature
> Affects Versions: 0.22.0
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Fix For: 0.22.0
>
>
> The HDFS Name service currently uses a single Namenode which limits its
> scalability. This is a master jira to track sub-jiras to address this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
