[
https://issues.apache.org/jira/browse/HBASE-24250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094713#comment-17094713
]
Andrey Elenskiy commented on HBASE-24250:
-----------------------------------------
> the critical problem is why GCMultipleMergedRegionsProcedure not work
It did work, there were just so many of them because catalog janitor kept
resubmitting it for the same regions over and over again.
> and then something when wrong and caused a different procedure to stall
We had an issue with running out of direct memory causing regionservers to
crashloop and master to keep resubmitting region assignment. I think it's a
separate issue from what I've addressed here.
> 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)
