[jira] [Comment Edited] (HBASE-24795) RegionMover should deal with unknown (split/merged) regions

["Sean Busbey (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167448#comment-17167448 ] 

Sean Busbey edited comment on HBASE-24795 at 7/29/20, 6:51 PM:
---------------------------------------------------------------

there's already the {{--noack}} flag that allows moving just those regions that are still around. Can you describe what you're proposing beyond that behavior?


was (Author: busbey):
there's already the {{--noack}} flag that should be enough?

> 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)