hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "genericqa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12555) HDFS federation should support configure secondary directory
Date Mon, 18 Dec 2017 04:28:00 GMT

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

genericqa commented on HDFS-12555:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} | {color:red}
HDFS-12555 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-12555 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12902587/HDFS-12555.003.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/22437/console |
| Powered by | Apache Yetus 0.7.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> 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
>    Affects Versions: 2.6.0
>         Environment: 2.6.0-cdh5.10.0
>            Reporter: luoge123
>            Assignee: luoge123
>             Fix For: 2.6.0
>
>         Attachments: HDFS-12555.001.patch, HDFS-12555.002.patch, HDFS-12555.003.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message