Laszlo Gaal created IMPALA-14603:
------------------------------------
Summary: Consecutive Jenkins runs using different Java versions on
the same worker can run with the wrong JDK version
Key: IMPALA-14603
URL: https://issues.apache.org/jira/browse/IMPALA-14603
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Affects Versions: Impala 5.0.0
Reporter: Laszlo Gaal
Assignee: Laszlo Gaal
Worker instances for Jenkins jobs can be, and often are reused for multiple job
executions if worker timeout for dismissal is high. When such a worker is
reused for jobs requesting different JDK versions (e.g. first job runs with JDK
8, then a second job runs with JDK17, or vice versa), the second job installs
its required JDK packages correctly using {{bin/bootstrap_system.sh}}, but the
run can be performed using the JDK version used by the previous job, which is
incorrect for the current job. The effects can range from incorrect test
results to the minicluster being unable to start, e.g. a Java17 JRE receiving
JDK8-specific startup options, which were deprecated and removed in Java17.
This was observed on Red Hat Linux derivatives.
Jobs should not only install their required Java versions, but also ensure that
the default invoked java and javac versions are in fact the ones they installed
for themselves. This means that the alternatives mechanism should be updated
after package installation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
