[jira] [Created] (IMPALA-5223) HBase/Zookeeper continues to be flaky on RHEL7

["Taras Bobrovytsky (JIRA)" <ji...@apache.org>]

Taras Bobrovytsky created IMPALA-5223:
-----------------------------------------

             Summary: HBase/Zookeeper continues to be flaky on RHEL7
                 Key: IMPALA-5223
                 URL: https://issues.apache.org/jira/browse/IMPALA-5223
             Project: IMPALA
          Issue Type: Bug
          Components: Infrastructure
    Affects Versions: Impala 2.8.0
            Reporter: Taras Bobrovytsky
            Priority: Blocker


There were several failures on RHEL7 recently.

{code}
Starting cluster services...
Stopping kudu
Stopping kms
Stopping yarn
Stopping hdfs
Starting hdfs (Web UI - http://localhost:5070)
Namenode started
Starting yarn (Web UI - http://localhost:8088)
Starting kms (Web UI - http://localhost:9600)
Starting kudu (Web UI - http://localhost:8051)
The cluster is running
 --> Starting HBase
HBase start attempt: 1/5
Killing any HBase processes possibly lingering from previous start attempts
Stopping Hbase
localhost: -------------------------------------------------------------------------------
localhost: # This image has been automatically created with ComodIT - http://comodit.com #
localhost: -------------------------------------------------------------------------------
localhost: 
localhost: starting zookeeper, logging to /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/repos/Impala/logs/cluster/hbase/hbase-jenkins-zookeeper-impala-boost-static-burst-slave-el7-0a08.vpc.cloudera.com.out
starting master, logging to /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/repos/Impala/logs/cluster/hbase/hbase-jenkins-master-impala-boost-static-burst-slave-el7-0a08.vpc.cloudera.com.out
starting regionserver, logging to /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/repos/Impala/logs/cluster/hbase/hbase-jenkins-1-regionserver-impala-boost-static-burst-slave-el7-0a08.vpc.cloudera.com.out
starting regionserver, logging to /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/repos/Impala/logs/cluster/hbase/hbase-jenkins-2-regionserver-impala-boost-static-burst-slave-el7-0a08.vpc.cloudera.com.out
starting regionserver, logging to /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/repos/Impala/logs/cluster/hbase/hbase-jenkins-3-regionserver-impala-boost-static-burst-slave-el7-0a08.vpc.cloudera.com.out
Contents of HDFS root: []
Connecting to Zookeeper host(s).
Success: <kazoo.client.KazooClient object at 0x7f5aecf06e10>
Waiting for HBase node: /hbase/master
Waiting for HBase node: /hbase/master
Waiting for HBase node: /hbase/master
Waiting for HBase node: /hbase/master
Waiting for HBase node: /hbase/master
Waiting for HBase node: /hbase/master
Waiting for HBase node: /hbase/master
Waiting for HBase node: /hbase/master
Failed while checking for HBase node: /hbase/master
Waiting for HBase node: /hbase/rs
Success: /hbase/rs
Stopping Zookeeper client
Could not get one or more nodes. Exiting with errors: 1
Error in /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/repos/Impala/testdata/bin/run-hbase.sh at line 129: ${CLUSTER_BIN}/check-hbase-nodes.py
Error in /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/repos/Impala/testdata/bin/run-all.sh at line 51: tee ${IMPALA_CLUSTER_LOGS_DIR}/run-hbase.log
+ echo 'buildall.sh ' -format '-snapshot_file /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/testdata/test-warehouse-SNAPSHOT/test-warehouse-cdh5-304-SNAPSHOT.tar.gz' '-metastore_snapshot_file /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/testdata/hive_metastore_snapshot/hive_impala_dump_cdh5-304.txt failed.'
buildall.sh  -format -snapshot_file /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/testdata/test-warehouse-SNAPSHOT/test-warehouse-cdh5-304-SNAPSHOT.tar.gz -metastore_snapshot_file /data/jenkins/workspace/impala-asf-master-exhaustive-rhel7/testdata/hive_metastore_snapshot/hive_impala_dump_cdh5-304.txt failed.
+ RET_VAL=1
{code}

This issue is similar to IMPALA-4733.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)