hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12499) dfs.namenode.shared.edits.dir property is currently namenode specific key
Date Tue, 31 Oct 2017 18:07:00 GMT

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

Hudson commented on HDFS-12499:
-------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13170 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/13170/])
HDFS-12499. dfs.namenode.shared.edits.dir property is currently namenode (arp: rev b922ba7393bd97b98e90f50f01b4cc664c44adb9)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSUtil.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
Revert "HDFS-12499. dfs.namenode.shared.edits.dir property is currently (wang: rev 5f681fa8216fb43dff8a3d21bf21e91d6c6f6d9c)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSUtil.java


> dfs.namenode.shared.edits.dir property is currently namenode specific key
> -------------------------------------------------------------------------
>
>                 Key: HDFS-12499
>                 URL: https://issues.apache.org/jira/browse/HDFS-12499
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: qjm
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>         Attachments: HDFS-12499.01.patch, HDFS-12499.02.patch
>
>
> HDFS + Federation cluster +QJM
> dfs.shared.edits.dir property can be set as
> 1. dfs.shared.edits.dir.<<nameserviceId>> 
> 2. dfs.shared.edits.dir.<<nameserviceId>> .<<namenodId>>
> Configuring both ways are supported currently. Option 2 should not be supported, as for
a particular nameservice quorum of journal nodes should be same.
> If option 2 is supported, users can configure for a nameservice Id which is having two
namenodes, they can configure different values for journal nodes. which is incorrect.
> Example:
> <property>
>     <name>dfs.nameservices</name>
>     <value>ns1,ns2</value>
>   </property>
>   <property>
>     <name>dfs.ha.namenodes.ns1</name>
>     <value>nn1,nn2</value>
>   </property>
>   <property>
>     <name>dfs.ha.namenodes.ns2</name>
>     <value>nn1,nn2</value>
>   </property>
> <property>
>     <name>dfs.namenode.shared.edits.dir.ns1.nn1</name>
>     <value>qjournal://mycluster-node-1:8485;mycluster-node-2:8485;mycluster-node-3:8485/ns1</value>
>   </property>
> <property>
>     <name>dfs.namenode.shared.edits.dir.ns1.nn1</name>
>     <value>qjournal://mycluster-node-3:8485;mycluster-node-4:8485;mycluster-node-5:8485/ns1</value>
>   </property>
>   <property>
>     <name>dfs.namenode.shared.edits.dir.ns2.nn1</name>
>     <value>qjournal://mycluster-node-1:8485;mycluster-node-2:8485;mycluster-node-3:8485/ns2</value>
>   </property>
>   <property>
>     <name>dfs.namenode.shared.edits.dir.ns2.nn1</name>
>     <value>qjournal://mycluster-node-3:8485;mycluster-node-4:8485;mycluster-node-5:8485/ns2</value>
>   </property>
> This jira is to discuss do we need to support 2nd option way of configuring or remove
it?



--
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