You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/07/14 18:28:00 UTC
[jira] [Updated] (HBASE-24316) GCMulitpleMergedRegionsProcedure is
not idempotent
[ https://issues.apache.org/jira/browse/HBASE-24316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-24316:
---------------------------------
Fix Version/s: (was: 2.4.0)
> GCMulitpleMergedRegionsProcedure is not idempotent
> ---------------------------------------------------
>
> Key: HBASE-24316
> URL: https://issues.apache.org/jira/browse/HBASE-24316
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.4.0
> Reporter: Huaxiang Sun
> Assignee: Huaxiang Sun
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> Currently deleteMergeQualifiers() is not idempotent. If two GCMulitpleMergedRegionsProcedures are run for the same merged child region, the second run will delete the row for the merge region from meta table and leave a hole. It needs to make sure it only deletes columns with merge qualifiers.
> [https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java#L1849]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)