IMPALA-7043: HBase split failure should not fail dataload

HBase splitting can fail due to changes in HBase code. It
is useful to still do tests even if HBase splitting failed.
As it is today, will abort if's invocation of fails.
No tests run, even though the HBase splitting affects only
a small portion of our tests.

This changes to keep going with
dataload if HBase splitting fails. It outputs the same
errors to the log as it would before this change.
It adds a message to explain that it is ignoring
the failure and there may be related test failures.

Change-Id: I7497fe8c9f1655a34b2743462d8b7248eb94554e
Reviewed-by: Philip Zeyliger <>
Tested-by: Impala Public Jenkins <>


Branch: refs/heads/2.x
Commit: 99e379dc57e561f476b3d35e5c52c0ae0f8ac767
Parents: bf7e766
Author: Joe McDonnell <>
Authored: Wed May 16 14:41:37 2018 -0700
Committer: Impala Public Jenkins <>
Committed: Thu May 17 22:03:02 2018 +0000

 testdata/bin/ | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/testdata/bin/ b/testdata/bin/
index a97a2e2..4d3928a 100755
--- a/testdata/bin/
+++ b/testdata/bin/
@@ -574,7 +574,11 @@ if [ "${TARGET_FILESYSTEM}" = "hdfs" ]; then
   # HBase splitting is only relevant for FE tests
   if [[ -z "$REMOTE_LOAD" ]]; then
-    run-step "Splitting HBase" create-hbase.log 
+    IGNORE_MSG="Ignoring this HBase splitting failure to allow dataload to 
complete and
+        tests to run. This failure will cause some frontend tests to fail, and 
it may
+        impact some HBase tests. Other tests are unaffected."
+    run-step "Splitting HBase" create-hbase.log 
${IMPALA_HOME}/testdata/bin/ \
+        || echo ${IGNORE_MSG}
   run-step "Creating internal HBase table" create-internal-hbase-table.log \

Reply via email to