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

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Impala 3.0, Impala 3.1.0, Impala 3.2.0, Impala 4.0.0, Impala 3.3.0, Impala 3.4.0, Impala 4.1.0, Impala 4.2.0
• Fix Version/s: Impala 4.3.0
• Epic Color: ghx-label-13
• Assignee: zhangqianqiong
• Reporter: zhangqianqiong
• Created: 09/Jul/23 05:01
• Updated: 15/Sep/23 18:38
• Resolved: 08/Sep/23 17:43

Description

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

After multiple tests, three failure scenarios were identified:

1. InternalException: couldn't execute a batch of exprs. The root cause is TProtocolException: Unrecognized type 97.
2. 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.
3. 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.

Issue Links

• Blocked: IMPALA-2202 InternalException: couldn't execute a batch of exprs
• is caused by: IMPALA-358 Double check release of JNI-allocated byte-strings