You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2019/01/12 20:16:00 UTC

[jira] [Commented] (HBASE-21706) Inconsistency of fs.defaultFS between active and standby masters

    [ https://issues.apache.org/jira/browse/HBASE-21706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741398#comment-16741398 ] 

stack commented on HBASE-21706:
-------------------------------

Thanks for reporting. Is this an HDP issue or do you see it in apache too? If you are confused and there is no clarifying doc, and it seems wrong, it probably is. On failover, does the new master find the right fs?  Thanks.

> Inconsistency of fs.defaultFS between active and standby masters
> ----------------------------------------------------------------
>
>                 Key: HBASE-21706
>                 URL: https://issues.apache.org/jira/browse/HBASE-21706
>             Project: HBase
>          Issue Type: Bug
>          Components: conf, master
>    Affects Versions: 1.1.2
>            Reporter: Lei Chen
>            Priority: Minor
>
> I'm using HDP-2.6.3.22-1 with HBase HA configured. I noticed that active and standby masters have different `fs.defaultFS` on their /conf pages.
>  Given `fs.defaultFS` is set to <scheme>:<authority> and `hbase.rootdir` is set to <scheme>:<authority>/<root-dir> in core-site.xml on all the hosts, it looks like standby masters has `fs.defaultFS` programatically set to the same value as `hbase.rootdir`. 
> For example, on a 3 heads cluster DEV-CLUSTER, my active master has the following line on the /conf page
> {code:java}
> <property><name>fs.defaultFS</name><value>hdfs://DEV-CLUSTER</value><source>programatically</source></property>
> {code}
> but standby masters has 
> {code:java}
> <property><name>fs.defaultFS</name><value>hdfs://DEV-CLUSTER/hbase-root</value><source>programatically</source></property>{code}
> Please correct me if this is not a bug but a feature, however I find this behavior surprising plus I cannot locate any related document.
> From a quick look at the code, the cause seems to be that standby masters got the property set in [HRegionServer.java|https://github.com/hortonworks/hbase-release/blob/HDP-2.6.3.22-tag/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java#L649-L652], and active master got it set in a different way in [MasterFileSystem.java|https://github.com/hortonworks/hbase-release/blob/HDP-2.6.3.22-tag/hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java#L132-L137].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)