[IMPALA-10278] impalad_executor Docker container fails to find JniUtil

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: Impala 4.0.0
• Fix Version/s: Impala 4.0.0
• Component/s: Frontend
• Target Version: Impala 4.0.0
• Epic Color: ghx-label-5
• Assignee: Joe McDonnell
• Reporter: Joe McDonnell
• Created: 23/Oct/20 02:50
• Updated: 28/Oct/20 01:14
• Resolved: 23/Oct/20 21:55

Description

When testing with the impalad_executor Docker container, I ran into a ClassNotFound on startup:

java.lang.NoClassDefFoundError: org/apache/impala/common/JniUtil
Caused by: java.lang.ClassNotFoundException: org.apache.impala.common.JniUtil
	at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
F1023 02:31:09.092646     1 init.cc:368] Failed to find JniUtil class.
. Impalad exiting.

This may be related to the docker size optimizations from https://issues.apache.org/jira/browse/IMPALA-10016 . JniUtil is something that would come from the frontend jar, which is not included for the executor image right now.

Using a small change that uses one coord_exec and two executors (https://gerrit.cloudera.org/#/c/16637/), this reproduces on the existing docker job: https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/

Issue Links

• relates to: IMPALA-10297 Use reduced set of jars for impalad_executor Docker image