You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2018/02/22 06:12:00 UTC
[jira] [Commented] (HBASE-20046) Reconsider the implementation for
serial replication
[ https://issues.apache.org/jira/browse/HBASE-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372451#comment-16372451 ]
Duo Zhang commented on HBASE-20046:
-----------------------------------
And I'm afraid there will be something wrong with the region replica feature... For rep_meta we use encoded region name as row key, but for other family meta, we use the region name for default replica as row key...
> Reconsider the implementation for serial replication
> ----------------------------------------------------
>
> Key: HBASE-20046
> URL: https://issues.apache.org/jira/browse/HBASE-20046
> Project: HBase
> Issue Type: New Feature
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
>
> When implementing HBASE-9465 we added two new families to meta table, one is rep meta and the other is rep_position. In general I think rep_meta is OK to put into meta table since it records the open and close sequence id for a region, but for rep_position, I think it should be put into another system table instead of meta table.
> This should be done before we finally release 2.0.0 or 1.5.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)