[
https://issues.apache.org/jira/browse/KUDU-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961668#comment-16961668
]
Alexey Serbin commented on KUDU-2986:
-------------------------------------
Another test is:
# Have a cluster with 1 master and 3 tablet servers running Kudu 1.10.0
# Shutdown master and one of the tablet servers
# Replace the binaries of the master and the tablet server with Kudu 1.11.0
binaries
# Start the master and the tablet server back, so it's now a cluster with
1.11.0 master, one 1.11.0 tablet server, and two 1.10.0 tablet servers
# Create a new table with replication factor 3 and multiple partitions
# Run {{kudu table statistics}} for the newly created table
The results are inconsistent for both the `live_row_count` and the
`on_disk_size` metrics. For example:
{noformat}
$ ./bin/kudu table statistics 10.17.240.17:9876
default.loadgen_auto_1fe440bbeb25446fb6f98bd9e0aa473a
TABLE default.loadgen_auto_1fe440bbeb25446fb6f98bd9e0aa473a
on disk size: 42139829
live row count: 1246
{noformat}
The row count should be 2000: that's how many rows were inserted when creating
the table.
However, the metrics become consistent after replacing the binaries of the rest
two tablet servers with Kudu 1.11.0, bringing all the cluster to 1.11.0 version:
{noformat}
$ ./bin/kudu table statistics 10.17.240.17:9876
default.loadgen_auto_1fe440bbeb25446fb6f98bd9e0aa473a
TABLE default.loadgen_auto_1fe440bbeb25446fb6f98bd9e0aa473a
on disk size: 67423947
live row count: 2000
{noformat}
> 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: client, master, metrics
> Affects Versions: 1.11.0
> Reporter: YifanZhang
> 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)
