[
https://issues.apache.org/jira/browse/IMPALA-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562297#comment-16562297
]
Sailesh Mukil commented on IMPALA-6644:
---------------------------------------
[~mkempanna] From a user point of view, is there a strong need to have the log
frequency configurable, instead of just keeping it as a constant: 60 seconds?
We're trying to avoid adding too many flags to the codebase, so making sure
that we absolutely need it before it's added to the codebase.
CC: [~poojanilangekar]
> 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-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
