[IMPALA-7061] PlannerTests should assign HBase splits as part of the test

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: Impala 2.13.0, Impala 3.1.0
• Fix Version/s: Impala 2.13.0, Impala 3.1.0
• Component/s: Frontend, Infrastructure
• Epic Color: ghx-label-7
• Assignee: Joe McDonnell
• Reporter: Joe McDonnell
• Created: 23/May/18 16:39
• Updated: 04/Sep/18 15:41
• Resolved: 31/May/18 16:29

Description

Some frontend PlannerTests rely on HBase tables being split into specific regions with those regions assigned to specific region servers. Right now, the HBase tables are created via the HBase shell with a single region, then they are populated via Hive DMLs, then there is a Java program that splits the tables into appropriate regions and assigns those regions to region servers. Once that is done, nothing is maintaining the assignments. The Java code for doing the splitting is hard to maintain and flaky. The assignments can sometimes drift due to rebalancing.

We should convert this to specify the splits at HBase table creation time. We should have the frontend PlannerTest do assignments at setup time to avoid flakiness due to rebalancing. This should move some flakiness out of dataload.

Issue Links

• is duplicated by: IMPALA-1995 Flaky test: PlannerTest.testHbase: splits for HBASE KEYRANGE not set up correctly.
• is related to: IMPALA-7119 HBase tests failing with RetriesExhausted and "RuntimeException: couldn't retrieve HBase table"
• is related to: IMPALA-7523 Planner Test failing with "Failed to assign regions to servers after 60000 millis."
• relates to: IMPALA-6776 Failed to assign hbase regions to servers
• relates to: IMPALA-1995 Flaky test: PlannerTest.testHbase: splits for HBASE KEYRANGE not set up correctly.