You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "zhangqianqiong (Jira)" <ji...@apache.org> on 2023/07/09 05:02:00 UTC

[jira] [Created] (IMPALA-12273) Deserialization failure, because of 'InternalException: couldn't execute a batch of exprs'

zhangqianqiong created IMPALA-12273:
---------------------------------------

             Summary: Deserialization failure, because of 'InternalException: couldn't execute a batch of exprs'
                 Key: IMPALA-12273
                 URL: https://issues.apache.org/jira/browse/IMPALA-12273
             Project: IMPALA
          Issue Type: Bug
    Affects Versions: Impala 4.2.0, Impala 4.1.0, Impala 3.4.0, Impala 3.3.0, Impala 4.0.0, Impala 3.2.0, Impala 3.1.0, Impala 3.0
            Reporter: zhangqianqiong
             Fix For: Impala 4.3.0
         Attachments: FeSupport.15b28f2002cd.impala.log.INFO.20230630-175220.28436, FeSupport.15b28f2002cd.impala.log.INFO.20230706-180457.2772, hs_err_pid12712.log

During stress testing, an anomalous behavior was observed: deserialization failures leading to SQL execution failures.

After multiple tests, three failure scenarios were identified:
 # InternalException: couldn't execute a batch of exprs. The root cause is TProtocolException: Unrecognized type 97.
 # InternalException: couldn't execute a batch of exprs. The root cause is TTransportException:  Cannot read. Remote side has closed. Tried to read 1 bytes, but only got 0 bytes.
 # JVM core dump, with the root cause being G1ParScanThreadState::copy_to_survivor_space(InCSetState, oopDesc*, markOopDesc*)+0x263.

By extracting a minimal test case, the above errors could be reproduced, ultimately indicating that the object returned by the native method in the Java code JNI invocation was prematurely gc.

 

The hs_err and log are attached.



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