[
https://issues.apache.org/jira/browse/IMPALA-14603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043196#comment-18043196
]
ASF subversion and git services commented on IMPALA-14603:
----------------------------------------------------------
Commit fe41448780c08ed0b7693ede3996a68ff1d76a60 in impala's branch
refs/heads/master from Laszlo Gaal
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=fe4144878 ]
IMPALA-14603: Force Java alternative after setup on Rocky and Red Hat Linux
Impala allows various Java versions to be selected for its build and
runtime environment when bin/bootstrap_system.sh is used to set up the
environment. Unfortunately this setup failed to affect the current Java
JRE and compiler tools on Red Hat Linux and compatibles (e.g. Rocky
Linux), because bootstrap_system.sh failed to set up the requested
version in the "alternatives" subsystem. The same failure was not
observed on Ubuntu versions, on that platform `update_java_alternatives`
was correctly run for the same purpose.
This patch adds calls to `alternatives` to set the JRE and JDK
environments to the requested version. This benefits automated test runs
in Impala's pre- and post-commit environments as well as individual
workstation setups.
Change-Id: I8972fb35b232830c6d8cf1125a7a8223547bd206
Reviewed-on: http://gerrit.cloudera.org:8080/23741
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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
> Priority: Critical
> Labels: broken-build
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
