[
https://issues.apache.org/jira/browse/HBASE-24250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097802#comment-17097802
]
niuyulin edited comment on HBASE-24250 at 5/2/20, 2:36 PM:
-----------------------------------------------------------
[~huaxiangsun] Maybe you forget add the Procedures Last round generate into
ongoingMergeProcedures? you cannot sure it finish in last round.
it can work, but when GCMultipleMergedRegionsProcedure finish or failed exit,
you must clean the Procedure in ongoingMergeProcedures
was (Author: niuyulin):
[~huaxiangsun] Maybe you forget add the Procedures Last round generate into
ongoingMergeProcedures, you cannot sure it finish in last round.
it can work, but when GCMultipleMergedRegionsProcedure finish or failed exit,
you must clean the Procedure in ongoingMergeProcedures
> CatalogJanitor resubmits GCMultipleMergedRegionsProcedure for the same region
> -----------------------------------------------------------------------------
>
> Key: HBASE-24250
> URL: https://issues.apache.org/jira/browse/HBASE-24250
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 2.2.4
> Environment: hdfs 3.1.3 with erasure coding
> hbase 2.2.4
> Reporter: Andrey Elenskiy
> Assignee: niuyulin
> Priority: Major
>
> If a lot of regions were merged (due to change of region sizes, for example),
> there can be a long backlog of procedures to clean up the merged regions. If
> going through this backlog is slower than the CatalogJanitor's scan interval,
> it will end resubmitting GCMultipleMergedRegionsProcedure for the same
> regions over and over again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
