[
https://issues.apache.org/jira/browse/HBASE-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248083#comment-13248083
]
Todd Lipcon commented on HBASE-5738:
------------------------------------
bq. The problem is that the HDFS client changed the fs.default.name property to
fs.defaultFS in HA.
That's not quite right -- the config key change was from 0.20 to 0.21, but the
old config key should still work. So I'm confused why this fixes the problem...
Also, this might break 0.20 (if it doesnt, then I'm suspicious of why this code
is there at all!)
> Using HBase with HA HDFS requires bogus hardcoded port value
> ------------------------------------------------------------
>
> Key: HBASE-5738
> URL: https://issues.apache.org/jira/browse/HBASE-5738
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.92.1, 0.94.0
> Reporter: Shaneal Manek
> Assignee: Shaneal Manek
> Attachments: HBASE-5738.patch
>
>
> When configuring HBase with HDFS HA, we currently have to have the 8020 port
> (regardless of what port HDFS is using for the namenode rpc address) in the
> following property in hbase-site.xml:
> {noformat}
> <property>
> <name>hbase.rootdir</name>
> <value>hdfs://ha-nn-uri:8020/hbase</value>
> </property>
> {noformat}
> Otherwise the master and regionservers will not start.
> The value in the above property should really just be
> "hdfs://ha-nn-uri/hbase" (replace "ha-nn-uri" with your uri and "hbase" with
> the name of the hbase directory in HDFS that you are using, as appropriate).
--
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
