[
https://issues.apache.org/jira/browse/KUDU-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019394#comment-17019394
]
LiFu He commented on KUDU-2986:
-------------------------------
Here is a confusing use case:
# we have a cluster with 1 master(1.12.x), 2 tservers(1.10.x) , and 1
tserver(1.12.x);
# create a table with single tablet and RF = 3;
# If the leader is on 1.12.x, we can see the statistics, but if the leader is
on 1.10.x, we can't see the statistics.:(
> 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)
