You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2012/07/31 22:50:40 UTC
[jira] [Assigned] (HDFS-3739) Not all HA props support
nameservice-id specific config
[ https://issues.apache.org/jira/browse/HDFS-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin Patrick McCabe reassigned HDFS-3739:
------------------------------------------
Assignee: Colin Patrick McCabe
> Not all HA props support nameservice-id specific config
> -------------------------------------------------------
>
> Key: HDFS-3739
> URL: https://issues.apache.org/jira/browse/HDFS-3739
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.0.0-alpha
> Reporter: E. Sammer
> Assignee: Colin Patrick McCabe
>
> Many parameters like dfs.client.failover.proxy.provider, dfs.namenode.rpc-address, and dfs.namenode.http-address support nameservice-id specific definition in an effort to support a single configuration file everywhere. Some HA properties, however, don't seem to support this. Specifically, dfs.namenode.shared.edits.dir, dfs.ha.fencing.methods, dfs.ha.automatic-failover.enabled, and ha.zookeeper.quorum (core-site) seem to have this issue (or are documented as such).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira