Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 31 Oct 2017 17:46:01 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13103453.1505866045000.113504.1509471961646@Atlassian.JIRA>
In-Reply-To: <JIRA.13103453.1505866045000@Atlassian.JIRA>
References: <JIRA.13103453.1505866045000@Atlassian.JIRA> <JIRA.13103453.1505866045971@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-12499) dfs.namenode.shared.edits.dir
 property is currently namenode specific key
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 31 Oct 2017 17:46:09 -0000


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

Andrew Wang commented on HDFS-12499:
------------------------------------

Sorry, I was off yesterday. I just checked, and Cloudera Manager actually does set it in style 2.

Two questions reviewing the JIRA:
* Is there some way to make this backwards compatible, like having one conf override the other?
* Is the rationale for this change to simplify the configuration options?

Since this doesn't look like a critical bug fix and it does have real world compatibility implications, I'm going to revert this while we discuss. I was planning on posting an RC for 3.0.0 GA this week.


> 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
>             Fix For: 3.0.0
>
>         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