[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Biju Nair updated HBASE-21816:
--
Labels: Replication (was: )
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Trivial
> Labels: Replication
> Fix For: 3.0.0, 2.2.0, 2.1.3, 2.3.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch,
> HBASE-21816-003.patch, HBASE-21816.master.001.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-21816:
--
Fix Version/s: (was: 2.1.4)
2.1.3
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Trivial
> Fix For: 3.0.0, 2.2.0, 2.1.3, 2.3.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch,
> HBASE-21816-003.patch, HBASE-21816.master.001.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki updated HBASE-21816:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Trivial
> Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.4
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch,
> HBASE-21816-003.patch, HBASE-21816.master.001.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki updated HBASE-21816:
-
Fix Version/s: 2.1.4
2.3.0
2.2.0
3.0.0
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Trivial
> Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.4
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch,
> HBASE-21816-003.patch, HBASE-21816.master.001.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki updated HBASE-21816:
-
Fix Version/s: (was: 3.0.0)
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Trivial
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch,
> HBASE-21816-003.patch, HBASE-21816.master.001.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Palanisamy updated HBASE-21816:
---
Attachment: HBASE-21816.master.001.patch
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch,
> HBASE-21816-003.patch, HBASE-21816.master.001.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-21816:
---
Priority: Trivial (was: Major)
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch,
> HBASE-21816-003.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Palanisamy updated HBASE-21816:
---
Attachment: HBASE-21816-003.patch
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Assignee: Karthik Palanisamy
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch,
> HBASE-21816-003.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Palanisamy updated HBASE-21816:
---
Priority: Major (was: Trivial)
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Palanisamy updated HBASE-21816:
---
Issue Type: Improvement (was: Bug)
> Print source cluster replication config directory
> -
>
> Key: HBASE-21816
> URL: https://issues.apache.org/jira/browse/HBASE-21816
> Project: HBase
> Issue Type: Improvement
> Components: Replication
>Affects Versions: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Palanisamy updated HBASE-21816:
---
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,
{code:java}
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:java}
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:java}
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}
was:
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}
> 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: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch
>
>
> 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,
> {code:java}
> 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:java}
> 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:java}
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Palanisamy updated HBASE-21816:
---
Attachment: HBASE-21816-002.patch
> 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: 3.0.0, 2.0.0
> Environment: NA
>Reporter: Karthik Palanisamy
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-21816-001.patch, HBASE-21816-002.patch
>
>
> 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)
[jira] [Updated] (HBASE-21816) Print source cluster replication config directory
[
https://issues.apache.org/jira/browse/HBASE-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Palanisamy updated HBASE-21816:
---
Attachment: HBASE-21816-001.patch
Status: Patch Available (was: Open)
> 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
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-21816-001.patch
>
>
> 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)
