[
https://issues.apache.org/jira/browse/HBASE-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372439#comment-16372439
]
Duo Zhang commented on HBASE-20046:
-----------------------------------
Just do not want to mess up meta since it does not need to be store in meta I
think. And also, in HBASE-19397, we have introduced a storage layer for
replication, I think the rep_position should also go this way. And now when
updating position, we need to update two places, one is the position for log
file on zk, and the other is the sequence id for region, which is in meta. We
need to deal with the inconsistency between these two places... So I think we
should store these two type of positions in one place, so we can make sure that
they are always consistent, if on zk, use multi, if in a system table, make it
not splittable and use atomic multi row mutations...
So maybe we can revert the feature from branch-2 and branch-1, and after we cut
branch-2.0, I will merge HBASE-19397-branch-2 back to branch-2, and reimplement
it based on the new replication interfaces and target the feature to 2.1. For
branch-1, as [~yangzhe1991] has already moved on so I'm afraid no one can take
care of the code so just give up supporting it on branch-1...
Thanks.
> Reconsider the meta schema change in HBASE-9465
> -----------------------------------------------
>
> Key: HBASE-20046
> URL: https://issues.apache.org/jira/browse/HBASE-20046
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 2.0.0, 1.5.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)
