hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1052) HDFS scalability with multiple namenodes
Date Thu, 28 Apr 2011 21:54:03 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026715#comment-13026715
] 

Suresh Srinivas commented on HDFS-1052:
---------------------------------------

TestFileConcurrentReader is a known failure. TestBackupNode, TestDatanodeBlockScanner and
TestDFSStorageStateRecovery pass on my machine. But if these tests continue to fail, I will
create a separate jira to address it.

> HDFS scalability with multiple namenodes
> ----------------------------------------
>
>                 Key: HDFS-1052
>                 URL: https://issues.apache.org/jira/browse/HDFS-1052
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: Block pool proposal.pdf, HDFS-1052.3.patch, HDFS-1052.4.patch, HDFS-1052.5.patch,
HDFS-1052.6.patch, HDFS-1052.patch, Mulitple Namespaces5.pdf, high-level-design.pdf
>
>
> HDFS currently uses a single namenode that limits scalability of the cluster. This jira
proposes an architecture to scale the nameservice horizontally using multiple namenodes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message