Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-21816

Print source cluster replication config directory

    XMLWordPrintableJSON

Details

    • Patch

    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));
}
}

      Attachments

        1. HBASE-21816.master.001.patch
          2 kB
          Karthik Palanisamy
        2. HBASE-21816-003.patch
          1 kB
          Karthik Palanisamy
        3. HBASE-21816-002.patch
          1 kB
          Karthik Palanisamy
        4. HBASE-21816-001.patch
          1 kB
          Karthik Palanisamy

        Issue Links

          links to

          Web Link Review Board (master)

          Activity

            People

              kpalanisamy Karthik Palanisamy
              kpalanisamy Karthik Palanisamy
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: