[
https://issues.apache.org/jira/browse/HDFS-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848235#action_12848235
]
Sanjay Radia commented on HDFS-1051:
------------------------------------
* Filing of this Jira does not exclude work on HA. These are independent issues.
* BTW there has been progress on HA:
** We have made a lot of progress in restarting a HDFS cluster - down from
several hours to less than 30 minutes for a 3K cluster over the last 2 years.
Reducing restart time is important for HA: cold, warm failover performs all or
part of the restart.
** Yahoo, along with reducing restart time, took a major step towards HA by
adding the backup namenode which synchronously gets the edit logs. This work
needs to be extended to do an actual failiover. For example dhr...@facebook
has taken an additional step in exploring manual failover.
* Hadoop is open source community project. Each contributor makes his/her own
priorities. Please help.
> 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
>
> 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.
