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

Hanisha Koneru commented on HDFS-12555:
---------------------------------------

[~luoge123], I submitted the patch so that it goes through a jenkins run. 
Thanks for working on this.

> HDFS federation should support configure secondary directory 
> -------------------------------------------------------------
>
>                 Key: HDFS-12555
>                 URL: https://issues.apache.org/jira/browse/HDFS-12555
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: federation
>         Environment: 2.6.0-cdh5.10.0
>            Reporter: luoge123
>             Fix For: 2.6.0
>
>         Attachments: HDFS-12555.001.patch, HDFS-12555.002.patch
>
>
> HDFS federation support multiple namenodes horizontally scales the file 
> system namespace. As the amount of data grows, using a single group of 
> namenodes to manage a single directory, namenode still achieves performance 
> bottlenecks. In order to reduce the pressure of namenode, we can split out 
> the secondary directory, and manager it by a new namenode. This is  
> transparent for users. 
> For example, nn1 only manager the /user directory, when nn1 achieve 
> performance bottlenecks, we can split out /user/hive directory, and ues nn2 
> to manager it.
> That means core-site.xml should support as follows configuration.
>    <property>
>        <name>fs.viewfs.mounttable.nsX.link./user</name>
>        <value>hdfs://nn1:8020/user</value>
>     </property>
>     <property>
>        <name>fs.viewfs.mounttable.nsX.link./user/hive</name>
>        <value>hdfs://nn2:8020/user/hive</value>
>     </property>



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to