[
https://issues.apache.org/jira/browse/HBASE-23294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975847#comment-16975847
]
Michael Stack commented on HBASE-23294:
---------------------------------------
I tested this by deleting all in 'info' column family for a row and then
running the cleaner. It output this:
{code}
ReplicationBarrierCleaner: Cleanup replication barriers: totalRows 3233,
cleanedRows 3233, deletedRows 0, deletedBarriers 1, deletedLastPushedSeqIds 0
{code}
That seems good. This was me forcing a run of the ReplicationCleanerChore via
fixMeta patch in HBASE-23307
Odd, [~zhangduo], is that when it ran on its natural cycle, it reported this
which seems odd:
{code}
hbase-cmf-data-hbase-MASTER-hbasemn005.sp07.siri.apple.com.log.out.2:2019-11-16
12:50:41,458 INFO
org.apache.hadoop.hbase.master.cleaner.ReplicationBarrierCleaner: Cleanup
replication barriers: totalRows 3233, cleanedRows 3233, deletedRows 0,
deletedBarriers 6464, deletedLastPushedSeqIds 0
{code}
How can it delete 6464 barriers when totalRows are 3233?
> ReplicationBarrierCleaner should delete all the barriers for a removed region
> which does not belong to any serial replication peer
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-23294
> URL: https://issues.apache.org/jira/browse/HBASE-23294
> Project: HBase
> Issue Type: Bug
> Components: master, Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.1.8, 2.2.3
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
