You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Bikramjeet Vig (JIRA)" <ji...@apache.org> on 2018/02/01 21:39:00 UTC
[jira] [Resolved] (IMPALA-6430) Log a detailed error message on
failure of MetricVerifier
[ https://issues.apache.org/jira/browse/IMPALA-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bikramjeet Vig resolved IMPALA-6430.
------------------------------------
Resolution: Fixed
[https://github.com/apache/impala/commit/cb2fa2475ee504c9d849a7a139b89c55cc59ce30]
IMPALA-6430: Log relevant debug pages if wait_for_metric_value times out
Log the memz, metrics and query page if the method wait_for_metric_value times out. This would help us understand the state of the defaulting impalad when the time out happens. Change-Id: I069dad48ede709c4114f4d7175861f98321be6cf Reviewed-on: [http://gerrit.cloudera.org:8080/9098]Reviewed-by: Bikramjeet Vig <bi...@cloudera.com> Tested-by: Impala Public Jenkins
> Log a detailed error message on failure of MetricVerifier
> ---------------------------------------------------------
>
> Key: IMPALA-6430
> URL: https://issues.apache.org/jira/browse/IMPALA-6430
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Affects Versions: Impala 2.12.0
> Reporter: Bikramjeet Vig
> Assignee: Bikramjeet Vig
> Priority: Major
> Fix For: Impala 2.12.0
>
>
> Log the memz, metrics and query debug pages on failure of the "wait_for_metric_value()" method in the impala-service python client. This would help us understand the state of impalad during that failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)