[
https://issues.apache.org/jira/browse/IMPALA-8714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sahil Takiar reassigned IMPALA-8714:
------------------------------------
Assignee: Sahil Takiar
> Metrics for tracking query failure reasons
> ------------------------------------------
>
> Key: IMPALA-8714
> URL: https://issues.apache.org/jira/browse/IMPALA-8714
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.3.0
> Reporter: Michael Ho
> Assignee: Sahil Takiar
> Priority: Major
> Labels: observability
>
> A query can fail for various reasons when run in Impala:
> - analysis failure (e.g. SQL syntax mistake)
> - access right issue (e.g. no privilege for certain ops on a table)
> - memory limit exceeded
> - scratch limit exceeded
> - EXEC_TIME_LIMIT_S exceeded
> - other guard rail exceeded
> - executor crashes
> - rpc failures
> - corrupted data files
> - client disconnected or session timed out
> This JIRA tracks the effort to explicitly classify query failures into some
> high level categories and expose them in the metrics. This should provide us
> a clearer view of what types of failures contribute the most to bad user
> experience for a given cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
