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 "Tim Armstrong (Jira)" <ji...@apache.org> on 2021/01/09 01:36:00 UTC
[jira] [Assigned] (IMPALA-3735) Add /fragments webpage
[ https://issues.apache.org/jira/browse/IMPALA-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong reassigned IMPALA-3735:
-------------------------------------
Assignee: (was: Henry Robinson)
> Add /fragments webpage
> ----------------------
>
> Key: IMPALA-3735
> URL: https://issues.apache.org/jira/browse/IMPALA-3735
> Project: IMPALA
> Issue Type: Task
> Components: Backend
> Affects Versions: Impala 2.6.0
> Reporter: Henry Robinson
> Priority: Minor
> Labels: observability
>
> It's hard at the moment to find out the following:
> # What fragments are running for a particular query
> # What fragments are running on a particular Impala backend
> This makes diagnosing a particular class of bugs, where a query has hung because of a single hung fragment, very painful. We should add {{/fragments}}, and also a per-query fragment list to the query details page.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org