[
https://issues.apache.org/jira/browse/IMPALA-13115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865841#comment-17865841
]
Quanlong Huang commented on IMPALA-13115:
-----------------------------------------
For executor crash, users could see different errors like this:
{code:java}
RPC from xxx:27010 to yyy:27010 failed
TransmitData() to yyy:27010 failed: Network error: recv error from unknown
peer: Transport endpoint is not connected (error 107){code}
We can consider handling these in new JIRAs.
> Always add the query id in the error message to clients
> -------------------------------------------------------
>
> Key: IMPALA-13115
> URL: https://issues.apache.org/jira/browse/IMPALA-13115
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Quanlong Huang
> Assignee: Xuebin Su
> Priority: Critical
> Labels: ramp-up
>
> We have some errors like "Failed due to unreachable impalad(s)". We should
> improve them to mention the query id, e.g. "Query ${query_id} failed due to
> unreachable impalad(s)". In a busy cluster, queries are flushed out quickly
> in the /queries page. Coordinator logs are also flushed out quickly. It's
> hard to find the query id there.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
