You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Wenzhe Zhou (Jira)" <ji...@apache.org> on 2024/05/24 23:02:00 UTC

[jira] [Created] (IMPALA-13107) Invalid TExecPlanFragmentInfo received by executor with instance number as 0

Wenzhe Zhou created IMPALA-13107:
------------------------------------

             Summary: Invalid TExecPlanFragmentInfo received by executor with instance number as 0
                 Key: IMPALA-13107
                 URL: https://issues.apache.org/jira/browse/IMPALA-13107
             Project: IMPALA
          Issue Type: Bug
          Components: Backend
            Reporter: Wenzhe Zhou
            Assignee: Wenzhe Zhou


In a customer report case, TExecPlanFragmentInfo received by executors with instance number as 0, like
{code:java}
impalad.executor.net.impala.log.INFO.20240522-160138.197583:I0523 00:59:16.892853 199528 control-service.cc:148] 624c47e9264ebb62:5aa89af300000000] ExecQueryFInstances(): query_id=624c47e9264ebb62:5aa89af300000000 coord=coordinator.net:27000 #instances=0
{code}
It seems KRPC messages were truncated due to KRPC failures, but truncation may not cause thrift deserialization error. The invalid TExecPlanFragmentInfo causes Impala daemon to crash.




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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org