[
https://issues.apache.org/jira/browse/HBASE-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171520#comment-17171520
]
Hudson commented on HBASE-24795:
--------------------------------
Results for branch master
[build #1804 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1804/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1804/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1804/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1804/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1804//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> 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
> Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0
>
>
> 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)
