hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "E. Sammer (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-3739) Not all HA props support nameservice-id specific config
Date Mon, 30 Jul 2012 21:09:36 GMT
E. Sammer created HDFS-3739:
-------------------------------

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


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

        

Mime
View raw message