tree a8ab30fefd1c37e03adf24704dead1998829ed7b
parent e716e76cccf59c2780571429b1b945d6bbc61b8d
author Joe McDonnell <joemcdonnell@cloudera.com> 1574449520 -0800
committer Impala Public Jenkins <impala-public-jenkins@cloudera.com> 1574476945 +0000

IMPALA-9165: Add back hard kill to kill-hbase.sh

The fix for IMPALA-9150 changed kill-hbase.sh to use HBase's
stop-hbase.sh script. Around this time, the GVO timeout issues
started. GVO can reuse machines, so we don't know what state
they may be in. If something failed to kill HBase processes,
the next job would need to be able to kill them even without
access to the last run's files / logs.

This restores the original kill logic to kill-hbase.sh, after
trying a graceful shutdown using HBase's stop-hbase.sh script.
The original kill logic doesn't rely on anything from the
filesystem to know about the existence of processes, so it
would handle machine reuse.

This also changes our Jenkins test scripts to shut down the
minicluster at the end.

Testing:
 - Started with a running minicluster, ran bin/clean.sh,
   then ran testdata/bin/kill-all.sh and verified that the
   java processes were gone

Change-Id: Ie2f0b342bcd1d8abea8ef923adbb54a14518a7a6
Reviewed-on: http://gerrit.cloudera.org:8080/14789
Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>