hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HDFS-12499) dfs.namenode.shared.edits.dir property is currently namenode specific key
Date Wed, 20 Sep 2017 00:27:03 GMT

     [ https://issues.apache.org/jira/browse/HDFS-12499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jitendra Nath Pandey reassigned HDFS-12499:
-------------------------------------------

    Assignee: Bharat Viswanadham

> 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
>
> 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 quoram of journal nodes should be same.
> 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