You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2020/09/30 16:58:00 UTC
[jira] [Commented] (HBASE-24981) Enable table replication fails
from 1.x to 2.x if table already exist at peer.
[ https://issues.apache.org/jira/browse/HBASE-24981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204880#comment-17204880 ]
Viraj Jasani commented on HBASE-24981:
--------------------------------------
Planning to commit this in a day unless there are any concerns.
> Enable table replication fails from 1.x to 2.x if table already exist at peer.
> -------------------------------------------------------------------------------
>
> Key: HBASE-24981
> URL: https://issues.apache.org/jira/browse/HBASE-24981
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 2.2.3
> Reporter: Sanjeet Nishad
> Assignee: Sanjeet Nishad
> Priority: Major
>
> If source is 1.x and peer is 2.x and a default table is created at source and also at peer, default table descriptors mismatch so the enable table replication fails with error :
>
> {code:java}
> Table t1 exists in peer cluster 1, but the table descriptors are not same when compared with source cluster. Thus can not enable the table's replication switch.{code}
> Following are the extra attributes set by default in 2.x:
> CACHE_DATA_ON_WRITE
> CACHE_INDEX_ON_WRITE
> CACHE_BLOOMS_ON_WRITE
> EVICT_BLOCKS_ON_CLOSE
> PREFETCH_BLOCKS_ON_OPEN.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)