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 "Dinesh Garg (JIRA)" <ji...@apache.org> on 2018/11/14 07:10:00 UTC
[jira] [Updated] (IMPALA-6741) Profiles of running queries should
tell last update time of counters
[ https://issues.apache.org/jira/browse/IMPALA-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Garg updated IMPALA-6741:
--------------------------------
Labels: ramp-up supportability (was: )
> 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
> Labels: ramp-up, supportability
>
> 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-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org