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 "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/08/30 06:19:00 UTC

[jira] [Commented] (IMPALA-6644) Add last heartbeat timestamp into Statestore metric

    [ https://issues.apache.org/jira/browse/IMPALA-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597094#comment-16597094 ] 

ASF subversion and git services commented on IMPALA-6644:
---------------------------------------------------------

Commit 8692bfbef657fe95da68e9dcaca9b49de331ccc3 in impala's branch refs/heads/master from poojanilangekar
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=8692bfb ]

IMPALA-6644: Add last heartbeat timestamp into Statestore metric

After this patch, the statestore keeps track of the time since the
last heartbeat for each subscriber. It is exposed as a subscriber
metric on the statestore debug page. It also adds a monitoring
thread that periodically checks the last heartbeat timestamp for
all subscribers and logs the IDs of those that have not been
updated since the last periodic check.

Testing: Added an end to end test to verify the 'sec_since_heartbeat'
metric of a slow subscriber.

Change-Id: I754adccc4569e8219d5d01500cccdfc8782953f7
Reviewed-on: http://gerrit.cloudera.org:8080/11052
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>


> 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
>
> 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