[
https://issues.apache.org/jira/browse/HBASE-23280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16972940#comment-16972940
]
Duo Zhang commented on HBASE-23280:
-----------------------------------
Now a table can be added to both serial or normal replication peer, so once the
replication_scope is set to 1, we need to write these barriers. And we can not
delete these things as you said in the description, the replication is
asynchronous. There is a background chore to clean these things up I believe?
Maybe there are some bugs in that chore too.
> Purge rep_barrier:seqnumDuringOpen on delete of Region
> ------------------------------------------------------
>
> Key: HBASE-23280
> URL: https://issues.apache.org/jira/browse/HBASE-23280
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: Michael Stack
> Priority: Major
>
> The Region GC Procedure only cleans the 'info' column family. We also write
> a rep_barrier column family as of HBASE-20115 . HBASE-20117 adds a chore to
> clean them up after-the-fact. I've not studied how rep_barrier works (There
> is a comment in MetaTableAccessor to add explaination).
> This issue is about adding the deletion of the rep_barrier content on region
> delete ([~zhangduo] will this mess up serial replication?).
> I want to clean out these rows. They occasionally can be misinterpreted in
> such as the hbck report as 'Orphan Regions' or in simple loading tools, we'll
> find the rep_barrier row and then fail because no accompanying
> info:regioninfo.
> Perhaps removing rep_barrier column family promptly is the wrong thing to
> do... we need the lag for replication to catch up.... Let me know [~zhangduo].
> Here is what they look like:
> {code}
> hbase(main):050:0> get 'hbase:meta',
> 'XXXX,22d0e538,1572669183985.6aa8710020b8a4f9ea290539fc254a76.'
> COLUMN
> CELL
> rep_barrier:seqnumDuringOpen
> timestamp=1573272944262, value=\x00\x00\x00\x00\x00\x00\x00\x02
> {code}
> They get updated on split and when location moves. I don't seem to be able to
> disable this facility -- it is on always. It also called 'unused' in title of
> HBASE-20117.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
