[HBASE-21706] Inconsistency of fs.defaultFS between active and standby masters

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.1.2
• Component/s: conf, master
• Assignee: Unassigned
• Reporter: Lei Chen
• Created: 11/Jan/19 20:48
• Updated: 13/Jan/19 02:18

Description

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

<property><name>fs.defaultFS</name><value>hdfs://DEV-CLUSTER</value><source>programatically</source></property>

but standby masters has 

<property><name>fs.defaultFS</name><value>hdfs://DEV-CLUSTER/hbase-root</value><source>programatically</source></property>

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, and active master got it set in a different way in MasterFileSystem.java.