[
https://issues.apache.org/jira/browse/KUDU-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024664#comment-17024664
]
Alexey Serbin commented on KUDU-2986:
-------------------------------------
Thank you [~helifu] for posting [the
fix|https://gerrit.cloudera.org/#/c/15071/] for the scenario described above!
I verified that with the fix, the scenario described
[above|https://issues.apache.org/jira/browse/KUDU-2986?focusedCommentId=17015578&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17015578].
> Incorrect value for the 'live_row_count' metric with pre-1.11.0 tables
> ----------------------------------------------------------------------
>
> Key: KUDU-2986
> URL: https://issues.apache.org/jira/browse/KUDU-2986
> Project: Kudu
> Issue Type: Bug
> Components: CLI, client, master, metrics
> Affects Versions: 1.11.0
> Reporter: YifanZhang
> Assignee: LiFu He
> Priority: Major
>
> When we upgraded the cluster with pre-1.11.0 tables, we got inconsistent
> values for the 'live_row_count' metric of these tables:
> When visiting masterURL:port/metrics, we got 0 for old tables, and got a
> positive integer for a old table with a newly added partition, which is the
> count of rows in the newly added partition.
> When getting table statistics via `kudu table statistics` CLI tool, we got 0
> for old tables and the old table with a new parition.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
