[
https://issues.apache.org/jira/browse/HDFS-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886386#action_12886386
]
Suresh Srinivas commented on HDFS-1052:
---------------------------------------
Gulin,
# An application could choose to use one of the namenodes as default file
system in its configuration. In that case /a/b/c will be resolved relative to
that namespace.
# There is a proposal in HDFS-1053 for client side mount tables, where client
can define it's namespace and how it maps to server side namespace. In that
case /a/b/c will be resolved in the context of client side mount table.
> 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, Mulitple Namespaces5.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.
