You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2020/07/29 18:49:00 UTC
[jira] [Commented] (HBASE-24795) RegionMover should deal with
unknown (split/merged) regions
[ https://issues.apache.org/jira/browse/HBASE-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167446#comment-17167446 ]
Viraj Jasani commented on HBASE-24795:
--------------------------------------
PR: [https://github.com/apache/hbase/pull/2172]
> RegionMover should deal with unknown (split/merged) regions
> -----------------------------------------------------------
>
> Key: HBASE-24795
> URL: https://issues.apache.org/jira/browse/HBASE-24795
> Project: HBase
> Issue Type: New Feature
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
>
> For a cluster with very high load, it is quite common to see flush/compaction happening every minute on each RegionServer. And we have quite high chances of multiple regions going through splitting/merging.
> RegionMover, while unloading all regions (graceful stop), writes down all regions to a local file and while loading them back (graceful start), ensures to bring every single region back from other RSs. While loading regions back, even if a single region can't be moved back, RegionMover considers load() failure. We miss out on possibilities of some regions going through split/merge process and the fact that not all regions written to local file might even exist anymore. Hence, RegionMover should gracefully handle moving any unknown region without marking load() failed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)