You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Huaxiang Sun (Jira)" <ji...@apache.org> on 2020/05/05 23:17:00 UTC
[jira] [Resolved] (HBASE-24323) Avoid two parallel running of
GCMulitpleMergedRegionsProcedure over the same region.
[ https://issues.apache.org/jira/browse/HBASE-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Huaxiang Sun resolved HBASE-24323.
----------------------------------
Resolution: Duplicate
> Avoid two parallel running of GCMulitpleMergedRegionsProcedure over the same region.
> ------------------------------------------------------------------------------------
>
> Key: HBASE-24323
> URL: https://issues.apache.org/jira/browse/HBASE-24323
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.4.0
> Reporter: Huaxiang Sun
> Priority: Major
>
> As [~stack]Â suggested in one of PRs, "This method is called from GCMergedRegionsProcedure and GCMulitpleMergedRegionsProcedure. I was wondering if we took a lock on the Region being Merged would it stop two overlapping GCs happening?"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)