[
https://issues.apache.org/jira/browse/HBASE-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167460#comment-17167460
]
Viraj Jasani edited comment on HBASE-24795 at 7/29/20, 7:19 PM:
----------------------------------------------------------------
At low level, --noack would ignore every Exception that occurs while moving
regions whereas --ack does not ignore any Exception but here, we are proposing
--ack to just ignore UnknownRegionException while moving a region.
was (Author: vjasani):
At low level, --noack would ignore every Exception that occurs while moving
regions while --ack does not ignore any Exception but we are proposing --ack to
just ignore UnknownRegionException while moving a region.
> RegionMover should deal with unknown (split/merged) regions
> -----------------------------------------------------------
>
> Key: HBASE-24795
> URL: https://issues.apache.org/jira/browse/HBASE-24795
> Project: HBase
> Issue Type: Improvement
> 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)
