Peter Rozsa created IMPALA-15410:
------------------------------------

             Summary: 4.5.2 Docker image catalogd and impalad fail at startup 
with NoClassDefFoundError
                 Key: IMPALA-15410
                 URL: https://issues.apache.org/jira/browse/IMPALA-15410
             Project: IMPALA
          Issue Type: Bug
    Affects Versions: Impala 4.5.2
            Reporter: Peter Rozsa
            Assignee: Michael Smith


The apache/impala:4.5.2-* images on Docker Hub  fail at startup. The JVM cannot 
load org.apache.hadoop.shaded.com.ctc.wstx.io.InputBootstrapper. The 4.5.0 
images with identical arguments start fine.
 
Steps to reproduce
No configuration files are mounted; the daemons run with image defaults.
{code:bash}
docker network create impala-repro
docker run -d --name statestored --network impala-repro \
  apache/impala:4.5.2-statestored -redirect_stdout_stderr=false -logtostderr
docker run --rm --network impala-repro apache/impala:4.5.2-catalogd \
  -redirect_stdout_stderr=false -logtostderr=true -state_store_host=statestored
{code}
Replacing 4.5.2 with 4.5.0 in the catalogd command starts normally.


catalogd exits about 10 seconds after start:
{noformat}
FileSystem: loadFileSystems failed error:
(unable to get root cause for java.lang.NoClassDefFoundError)
(unable to get stack trace for java.lang.NoClassDefFoundError)
getJNIEnv: getGlobalJNIEnv failed
I0923 14:28:24.841758     1 webserver.cc:408] Starting webserver on 
0.0.0.0:25020
F0923 14:28:24.899987     1 catalog.cc:89] NoClassDefFoundError: 
org/apache/hadoop/shaded/com/ctc/wstx/io/InputBootstrapper
CAUSED BY: ClassNotFoundException: 
org.apache.hadoop.shaded.com.ctc.wstx.io.InputBootstrapper
. Impalad exiting.
{noformat}
impalad_coordinator and impalad_executor fail identically (libhdfs 
loadFileSystems hits the same NoClassDefFoundError).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to