[HBASE-21816] Print source cluster replication config directory

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 2.0.0
• Fix Version/s: 3.0.0-alpha-1, 2.2.0, 2.1.3, 2.3.0
• Component/s: Replication
• Labels: Replication

Environment

NA

• Flags: Patch
• Assignee: Karthik Palanisamy
• Reporter: Karthik Palanisamy
• Created: 01/Feb/19 02:03
• Updated: 12/May/19 19:44
• Resolved: 08/Feb/19 05:16

Description

User may get confused, to understanding our HBase configurations which are loaded for replication. Sometimes, User may place source and destination cluster conf under "/etc/hbase/conf" directory. It will create uncertainty because our log points that all the configurations are co-located.

 

Existing Logs, 

INFO  [RpcServer.FifoWFPBQ.replication.handler=2,queue=0,port=16020] regionserver.DefaultSourceFSConfigurationProvider: Loading source cluster HDP1 file system configurations from xml files under directory /etc/hbase/conf/

But it should be something like,

INFO  [RpcServer.FifoWFPBQ.replication.handler=2,queue=0,port=16020] regionserver.DefaultSourceFSConfigurationProvider: Loading source cluster HDP1 file system configurations from xml files under directory /etc/hbase/conf/HDP1

 

This jira only to change the log-line, no issue with the functionality. 

File confDir = new File(replicationConfDir, replicationClusterId);
String[] listofConfFiles = FileUtil.list(confDir);
for (String confFile : listofConfFiles) {
if (new File(confDir, confFile).isFile() && confFile.endsWith(XML)) {
// Add all the user provided client conf files
sourceClusterConf.addResource(new Path(confDir.getPath(), confFile));
}
}

Issue Links

• links to: Review Board (master)