hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "NITIN VERMA (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17460) enable_table_replication can not perform cyclic replication of a table
Date Tue, 17 Jan 2017 22:06:26 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

NITIN VERMA updated HBASE-17460:
    Status: In Progress  (was: Patch Available)

Example of new functionality added:
hbase(main):014:0> enable_table_replication 'table1'
The replication of table 'table1' successfully enabled
Took 0.5180 seconds

hbase(main):016:0> enable_table_replication 'table1'

ERROR: Table table1 has replication already enabled for atleast one Column Family.

Here is some help for this command:
Enable a table's replication switch.


  hbase> enable_table_replication 'table_name'

Took 0.1180 seconds

> enable_table_replication can not perform cyclic replication of a table
> ----------------------------------------------------------------------
>                 Key: HBASE-17460
>                 URL: https://issues.apache.org/jira/browse/HBASE-17460
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: NITIN VERMA
>            Assignee: NITIN VERMA
>              Labels: replication
>         Attachments: HBASE-17460.patch, HBASE-17460_v2.patch
>   Original Estimate: 96h
>  Remaining Estimate: 96h
> The enable_table_replication operation is broken for cyclic replication of HBase table
as we compare all the properties of column families (including REPLICATION_SCOPE). 
> Below is exactly what happens:
> 1.  Running "enable_table_replication 'table1'  " opeartion on first cluster will set
the REPLICATION_SCOPE of all column families to peer id '1'. This will also create a table
on second cluster where REPLICATION_SCOPE is still set to peer id '0'.
> 2. Now when we run "enable_table_replication 'table1'" on second cluster, we compare
all the properties of table (including REPLICATION_SCOPE_, which obviously is different now.

> I am proposing a fix for this issue where we should avoid comparing REPLICATION_SCOPE
inside HColumnDescriotor::compareTo() method, especially when replication is not already enabled
on the desired table.
> I have made that change and it is working. I will submit the patch soon.

This message was sent by Atlassian JIRA

View raw message