[
https://issues.apache.org/jira/browse/IMPALA-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sahil Takiar resolved IMPALA-9229.
----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
Marking as resolved. The Web UI improvements are tracked in a separate JIRA.
> Link failed and retried runtime profiles
> ----------------------------------------
>
> Key: IMPALA-9229
> URL: https://issues.apache.org/jira/browse/IMPALA-9229
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Critical
> Fix For: Impala 4.0
>
>
> There should be a way for clients to link the runtime profiles from failed
> queries to all retry attempts (whether successful or not), and vice versa.
> There are a few ways to do this:
> * The simplest way would be to include the query id of the retried query in
> the runtime profile of the failed query, and vice versa; users could then
> manually create a chain of runtime profiles in order to fetch all failed /
> successful attempts
> * Extend TGetRuntimeProfileReq to include an option to fetch all runtime
> profiles for the given query id + all retry attempts (or add a new Thrift
> call TGetRetryQueryIds(TQueryId) which returns a list of retried ids for a
> given query id)
> * The Impala debug UI should include a simple way to view all the runtime
> profiles of a query (the failed attempts + all retry attempts) side by side
> (perhaps the query_profile?query_id profile should include tabs to easily
> switch between the runtime profiles of each attempt)
> These are not mutually exclusive, and it might be good to stage these changes.
--
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
