[
https://issues.apache.org/jira/browse/IMPALA-13107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenzhe Zhou updated IMPALA-13107:
---------------------------------
Description:
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}
>From the collected profile, there was no fragment with instance number as 0 in
>the query plan so coordinator should not send task to executor with number of
>instances as 0. Executor log files showed that there were lots of KRPC errors
>around the time when receiving invalid TExecPlanFragmentInfo. It seems KRPC
>messages were truncated due to KRPC failures, but truncation might not cause
>thrift deserialization error. The invalid TExecPlanFragmentInfo caused Impala
>daemon to crash when the query was started on executor.
was:
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.
> 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
> Priority: Major
>
> 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}
> From the collected profile, there was no fragment with instance number as 0
> in the query plan so coordinator should not send task to executor with number
> of instances as 0. Executor log files showed that there were lots of KRPC
> errors around the time when receiving invalid TExecPlanFragmentInfo. It seems
> KRPC messages were truncated due to KRPC failures, but truncation might not
> cause thrift deserialization error. The invalid TExecPlanFragmentInfo caused
> Impala daemon to crash when the query was started on executor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
