[
https://issues.apache.org/jira/browse/IMPALA-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980662#comment-16980662
]
ASF subversion and git services commented on IMPALA-9165:
---------------------------------------------------------
Commit 4c09975c14f624028100e9940526a111897846cb in impala's branch
refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=4c09975 ]
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 <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Precommit jobs getting stuck in testdata/bin/create-hbase.sh
> ------------------------------------------------------------
>
> Key: IMPALA-9165
> URL: https://issues.apache.org/jira/browse/IMPALA-9165
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.4.0
> Reporter: Joe McDonnell
> Priority: Blocker
> Labels: broken-build
>
> Several of our precommit jobs have been getting stuck and cancelled with this
> log:
> {noformat}
> 01:54:19 /home/ubuntu/Impala/testdata/target
> 01:54:19 SUCCESS, data generated into /home/ubuntu/Impala/testdata/target
> 01:54:20 Executing: create-load-data.sh
> 01:54:20 Generating HBase data (logging to
> /home/ubuntu/Impala/logs/data_loading/create-hbase.log)...
> 11:23:26 FATAL: Unable to delete script file
> /tmp/jenkins4199210326564796706.sh
> 11:23:26 java.lang.InterruptedException
> 11:23:26 at java.lang.Object.wait(Native Method)
> 11:23:26 at hudson.remoting.Request.call(Request.java:177)
> 11:23:26 at hudson.remoting.Channel.call(Channel.java:956)
> 11:23:26 at hudson.FilePath.act(FilePath.java:1070)
> 11:23:26 at hudson.FilePath.act(FilePath.java:1059)
> 11:23:26 at hudson.FilePath.delete(FilePath.java:1540)
> 11:23:26 at
> hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123)
> 11:23:26 at
> hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
> 11:23:26 at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 11:23:26 at
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
> 11:23:26 at hudson.model.Build$BuildExecution.build(Build.java:206)
> 11:23:26 at hudson.model.Build$BuildExecution.doRun(Build.java:163)
> 11:23:26 at
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
> 11:23:26 at hudson.model.Run.execute(Run.java:1818)
> 11:23:26 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> 11:23:26 at
> hudson.model.ResourceController.execute(ResourceController.java:97)
> 11:23:26 at hudson.model.Executor.run(Executor.java:429){noformat}
> This indicates that the job is getting stuck inside
> testdata/bin/create-hbase.sh. The logs are not available, because the job
> gets cancelled.
> Some example jobs with this problem:
> [https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/8847/]
> [https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/8762/]
> [https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/8850/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
