[
https://issues.apache.org/jira/browse/HBASE-19499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288438#comment-16288438
]
Esteban Gutierrez edited comment on HBASE-19499 at 12/12/17 11:12 PM:
----------------------------------------------------------------------
[~stack] pointed out to HBASE-18511. We cannot just remove that condition, but
we if {{hbase.balancer.tablesOnMaster.systemTablesOnly}} and
{{hbase.balancer.tablesOnMaster}} are enabled we can be more flexible in order
to avoid that failure.
was (Author: esteban):
[~stack] pointed out to HBASE-18511. We cannot just remove that test, but we if
{{hbase.balancer.tablesOnMaster.systemTablesOnly}} and
{{hbase.balancer.tablesOnMaster}} are enabled we can be more flexible in order
to avoid that failure.
> RegionMover#stripMaster is not longer necessary in RegionMover
> --------------------------------------------------------------
>
> Key: HBASE-19499
> URL: https://issues.apache.org/jira/browse/HBASE-19499
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Esteban Gutierrez
>
> Probably this is the first of few issues found during some tests with
> RegionMover. After HBASE-13014 we ship the new RegionMover tool but it
> currently assumes that master will be hosting regions so it attempts to
> remove master from the list and that causes an issue similar to this:
> {code}
> 17/12/12 11:01:06 WARN util.RegionMover: Could not remove master from list of
> RS
> java.lang.Exception: Server host1.example.com:22001 is not in list of online
> servers(Offline/Incorrect)
> at
> org.apache.hadoop.hbase.util.RegionMover.stripServer(RegionMover.java:818)
> at
> org.apache.hadoop.hbase.util.RegionMover.stripMaster(RegionMover.java:757)
> at
> org.apache.hadoop.hbase.util.RegionMover.access$1800(RegionMover.java:78)
> at
> org.apache.hadoop.hbase.util.RegionMover$Unload.call(RegionMover.java:339)
> at
> org.apache.hadoop.hbase.util.RegionMover$Unload.call(RegionMover.java:314)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Basicaly
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
