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 2018/11/19 23:08:00 UTC
[jira] [Resolved] (IMPALA-7857) Log more information about
statestore failure detector
[ https://issues.apache.org/jira/browse/IMPALA-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-7857.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> Log more information about statestore failure detector
> ------------------------------------------------------
>
> Key: IMPALA-7857
> URL: https://issues.apache.org/jira/browse/IMPALA-7857
> Project: IMPALA
> Issue Type: Bug
> Components: Distributed Exec
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: statestore, supportability
> Fix For: Impala 3.2.0
>
>
> For debugging heartbeat failures (or non-failures) it would be useful to log enough information to infer the current state of the failure detector from logs. Specifically:
> * Upon a failure, we should log the number of consecutive failures according to the failure detector. And also maybe how many failures remain until it's considered to be failed.
> * We should log when the failure count is reset to 0 by a successful heartbeat.
> Currently if there are occasional failures it's hard to tell with certainty whether it was reset correctly.
--
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