[
https://issues.apache.org/jira/browse/HDFS-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410396#comment-15410396
]
Amithsha commented on HDFS-1052:
--------------------------------
And
By Default i am mentioning the both the namenodes IP's in Conf
so why the code can take that in for loop and search blockLoction like this
if not getBlockLocation():
go to second nn
> 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: namenode
> Affects Versions: 0.22.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.23.0
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
