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 "Pooja Nilangekar (JIRA)" <ji...@apache.org> on 2018/08/30 16:48:00 UTC
[jira] [Resolved] (IMPALA-6644) Add last heartbeat timestamp into
Statestore metric
[ https://issues.apache.org/jira/browse/IMPALA-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pooja Nilangekar resolved IMPALA-6644.
--------------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Add last heartbeat timestamp into Statestore metric
> ---------------------------------------------------
>
> Key: IMPALA-6644
> URL: https://issues.apache.org/jira/browse/IMPALA-6644
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.11.0
> Reporter: Mala Chikka Kempanna
> Assignee: Pooja Nilangekar
> Priority: Minor
> Labels: ramp-up, supportability
> Fix For: Impala 3.1.0
>
>
> In the latest and previous versions, statestore in it's default logging reports only when it fails to send heartbeat to any host.
> There is no way to confirm if Statestore is indeed continuing to heartbeat in all passing conditions, except for turning on debug logs, which becomes too noisy. But at the same time its important to know statestore is indeed heartbeating.
> The suggestion here is to add a metric in statestore metric page and also print the same in log every once in a minute(or any configurable time-frequency), reporting the last heartbeat timestamp and last heartbeat host(optional).
>
>
>
--
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