[
https://issues.apache.org/jira/browse/HDFS-12499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175205#comment-16175205
]
Bharat Viswanadham edited comment on HDFS-12499 at 9/21/17 5:59 PM:
--------------------------------------------------------------------
Hi [~arpitagarwal]
Thank your for your comments.
This Jira is created from discussion and review of HDFS-12486 jira.
As if it is namenode specific, there can be chances of configuring different
journanl nodes for different namenodes in a same nameservice. To avoid that
kind of situation, this change can be helpful. If there is any other reason for
this, I am also not completely sure.
And also referring HDFS-2934, in that jira comments also it is mentioned
dfs.namenode.shared.edits.dir is a nameservice specific from comments, instead
of configuring it as namenode specific.
was (Author: bharatviswa):
Hi [~arpitagarwal]
Thank your for your comments.
This Jira is created from discussion and review of HDFS-12486 jira.
As if it is namenode specific, there can be chances of configuring different
journanl nodes for different namenodes in a same nameservice. To avoid that
kind of situation, this change can be helpful. If there is any other reason for
this, I am also not completely sure.
And also referring https://issues.apache.org/jira/browse/HDFS-2934, in that
jira comments also it is mentioned dfs.namenode.shared.edits.dir is a
nameservice specific from comments, instead of configuring it as namenode
specific.
> 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
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Labels: Incompatible
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
