Karthik Palanisamy created HBASE-21816:
------------------------------------------
Summary: Print source cluster replication config directory
Key: HBASE-21816
URL: https://issues.apache.org/jira/browse/HBASE-21816
Project: HBase
Issue Type: Bug
Components: Replication
Affects Versions: 2.0.0, 3.0.0
Environment: NA
Reporter: Karthik Palanisamy
Fix For: 3.0.0
We 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,
{code}
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/
{code}
But it should be something like,
{code}
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
{code}
This jira only to change the log-line, no issue with the functionality.
{code}
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));
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
