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 2020/01/21 21:07:00 UTC

[jira] [Assigned] (IMPALA-6214) Determine and warn about stuck fragment instances

     [ https://issues.apache.org/jira/browse/IMPALA-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong reassigned IMPALA-6214:
-------------------------------------

    Assignee:     (was: Pranay Singh)

> Determine and warn about stuck fragment instances
> -------------------------------------------------
>
>                 Key: IMPALA-6214
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6214
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>            Reporter: Lars Volker
>            Priority: Major
>              Labels: observability, supportability
>
> It would be great to have a programmatic way to determine if a fragment instance is hung by checking if it’s producing rows periodically. A fragment instance can appear to be not making progress because its input operator / fragment may be hung (e.g.the probe side of a join will not be able to make much progress until the build side is done and the build side itself could be another chain of joins). It'd be much easier to resolve this dependency chain programmatically to find the root of the cascade of delay.
> Details of algorithm are still unclear. It may be easier to include exec node states in query profile and analyze those, but this probably requires taking multiple snapshots of the query profiles over time.



--
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