[
https://issues.apache.org/jira/browse/IMPALA-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540717#comment-17540717
]
Quanlong Huang commented on IMPALA-1995:
----------------------------------------
Saw this again:
https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/16513
https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/16522
I think one solution is always moving the regions to the expected RegionServers
using
{code:java}
hbase> move 'ENCODED_REGIONNAME', 'SERVER_NAME'
{code}
[https://learnhbase.wordpress.com/2013/03/02/hbase-shell-commands/]
|*move*|Move a region. Optionally specify target regionserver else we choose one
at random. NOTE: You pass the encoded region name, not the region name so
this command is a little different to the others. The encoded region name
is the hash suffix on region names: e.g. if the region name were
TestTable,0094429456,1289497600452.527db22f95c8a9e0116f0cc13c680396. then
the encoded region name portion is 527db22f95c8a9e0116f0cc13c680396
A server name is its host, port plus startcode. For example:
host187.example.com,60020,1289493121758
Examples:hbase> move ‘ENCODED_REGIONNAME’
*hbase> move ‘ENCODED_REGIONNAME’, ‘SERVER_NAME’*|
> Flaky test: PlannerTest.testHbase: splits for HBASE KEYRANGE not set up
> correctly.
> ----------------------------------------------------------------------------------
>
> Key: IMPALA-1995
> URL: https://issues.apache.org/jira/browse/IMPALA-1995
> Project: IMPALA
> Issue Type: Task
> Components: Frontend
> Affects Versions: Impala 2.3.0, Impala 3.2.0
> Reporter: Alexander Behm
> Assignee: Joe McDonnell
> Priority: Critical
> Labels: broken-build, flaky, test-infra
> Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> Looks like testdata/bin/split-hbase.sh does not always set up the ranges in
> the way we want. See failure below.
> Example run:
> http://sandbox.jenkins.cloudera.com/job/impala-master-cdh5-trunk/1090/
> {code}
> Stack Trace:
> java.lang.AssertionError: section SCANRANGELOCATIONS of query:
> select * from functional_hbase.alltypessmall
> where id < 5
> actual result doesn't match expected result:
> HBASE KEYRANGE port=16202 3:7
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> HBASE KEYRANGE port=16203 7:<unbounded>
> HBASE KEYRANGE port=16203 <unbounded>:3
> NODE 0:
> expected:
> HBASE KEYRANGE port=16201 <unbounded>:3
> HBASE KEYRANGE port=16202 3:7
> HBASE KEYRANGE port=16203 7:<unbounded>
> NODE 0:
> section SCANRANGELOCATIONS of query:
> select * from functional_hbase.stringids
> where id < '5'
> and tinyint_col = 5
> actual result doesn't match expected result:
> HBASE KEYRANGE port=16201 1:3
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> HBASE KEYRANGE port=16202 3:5
> HBASE KEYRANGE port=16203 <unbounded>:1
> NODE 0:
> expected:
> HBASE KEYRANGE port=16201 <unbounded>:3
> HBASE KEYRANGE port=16202 3:5
> NODE 0:
> section SCANRANGELOCATIONS of query:
> select * from functional_hbase.alltypesagg
> where bigint_col is not null and bool_col = true
> actual result doesn't match expected result:
> HBASE KEYRANGE port=16201 1:3
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> HBASE KEYRANGE port=16202 3:7
> HBASE KEYRANGE port=16203 7:<unbounded>
> HBASE KEYRANGE port=16203 <unbounded>:1
> NODE 0:
> expected:
> HBASE KEYRANGE port=16201 <unbounded>:3
> HBASE KEYRANGE port=16202 3:7
> HBASE KEYRANGE port=16203 7:<unbounded>
> NODE 0:
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
