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:27:00 UTC
[jira] [Updated] (HBASE-24369) Provide more information about
merged child regions in Hbck Overlaps section, which cannot be fixed
immediately
[ https://issues.apache.org/jira/browse/HBASE-24369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-24369:
---------------------------------
Fix Version/s: (was: 2.4.0)
> Provide more information about merged child regions in Hbck Overlaps section, which cannot be fixed immediately
> -----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-24369
> URL: https://issues.apache.org/jira/browse/HBASE-24369
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 2.3.0
> Reporter: Huaxiang Sun
> Assignee: Huaxiang Sun
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
> Attachments: Screen Shot 2020-05-21 at 11.14.48 AM.png
>
>
> Right now, in Master's hbck page, pairs of overlap regions are listed.
> with Hbck2 -fixMeta, it will merge these overlap regions. However, if one of the region is a newly merged child region and GC has not kicked in yet, they are not fixable (merge will fail).
> Users get confused as why after HBCK2 -fixMeta and still there are overlaps. To avoid this confusion, propose a new subsection saying that master is doing GC on these regions and these regions cannot be fixed/merged at this moment, wait until these regions are ready (not showing up in this subsection) to start the fix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)