[
https://issues.apache.org/jira/browse/HDFS-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851499#action_12851499
]
Doug Cutting commented on HDFS-1052:
------------------------------------
If I follow the document, the initial implementation can confine its changes to
the datanode: the namenode need not initially be aware of block pools, only the
datanode. Is that correct? If so, I like that simplification.
> 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 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.
-
You can reply to this email to add a comment to the issue online.