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 "Vincent Tran (JIRA)" <ji...@apache.org> on 2018/08/27 16:06:00 UTC
[jira] [Commented] (IMPALA-6075) Add Impala daemon metric for
catalog version
[ https://issues.apache.org/jira/browse/IMPALA-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593879#comment-16593879 ]
Vincent Tran commented on IMPALA-6075:
--------------------------------------
[~pranay_singh],
Is this change meant to expose the catalog version currently used by a given Impala Daemon as catalog.curr-topic?
It looks like catalog.curr-topic tracks the latest topic version number that statestore is operating on, not necessarily what the Impala Daemon is using.
> Add Impala daemon metric for catalog version
> --------------------------------------------
>
> Key: IMPALA-6075
> URL: https://issues.apache.org/jira/browse/IMPALA-6075
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 2.10.0
> Reporter: Tim Armstrong
> Assignee: Pranay Singh
> Priority: Major
> Labels: observability
> Fix For: Impala 3.0, Impala 2.12.0
>
>
> [~jackowaya] was investigating a metadata inconsistency issue and it would have been useful to have a metric to that exposes the catalog version that the daemon has. You can see the oldest version on the topics page on the statestored, which is sometimes helpful, but that doesn't tell you whether a particular coordinator has a stale catalog.
--
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