[
https://issues.apache.org/jira/browse/IMPALA-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641646#comment-16641646
]
Balazs Jeszenszky commented on IMPALA-6741:
-------------------------------------------
[~kwho] Having elapsed time can be unreliable in case the coordinator itself
gets stuck. Having last update timestamp is more robust but harder to
interpret, and elapsed time would probably work more than 99% of the time.
Ideally, I think we should include both, e.g. {{Last update time <timestamp>
(<elapsed time> ago)}}.
> Profiles of running queries should tell last update time of counters
> --------------------------------------------------------------------
>
> Key: IMPALA-6741
> URL: https://issues.apache.org/jira/browse/IMPALA-6741
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Balazs Jeszenszky
> Assignee: Michael Ho
> Priority: Major
>
> When looking at the profile of a running query, it's impossible to tell the
> degree of accuracy. We've seen issues both with instances not checking in
> with the coordinator for a long time, and with hung instances that never
> update their counters. There are some specific issues as well, see
> IMPALA-5200. This means that profiles taken off of running queries can't be
> used perf troubleshooting with confidence.
> Ideally, Impala should guarantee counters to be written at a certain
> interval, and warn for counters or instances that are out of sync for some
> reason.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
