[ 
https://issues.apache.org/jira/browse/KUDU-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961686#comment-16961686
 ] 

Alexey Serbin commented on KUDU-2986:
-------------------------------------

One more simple test scenario:
# Have a cluster with 1 master and 3 tablet servers running Kudu 1.10.0
# Create a table with multiple tablets and replication factor of 3 (RF=3)
# Shutdown master
# Replace `kudu-master` with new binary of 1.11.0 version
# Start the master
# Check the `masterWebServerURL/metrics` page for the number of live rows for 
the table created at step 2
# Run `kudu tablet statistics` for the table created at step 2

As I understand, it's expected that the `live_row_count` metric value would be 
reported as invalid (N/A) in both the master's Web UI and kudu CLI output.  
However, that's not the case.

>From embedded webserver:
{noformat}
    {
        "type": "table",
        "id": "b3224dd995ba41f8869d5d2b3deaba4c",
        "attributes": {
            "table_name": 
"default.loadgen_auto_0867c7e10d894cabbe5536507b80b9d1"
        },
        "metrics": [
            {
                "name": "live_row_count",
                "value": 0
            },
            {
                "name": "on_disk_size",
                "value": 0
            }
        ]
    }
{noformat}

>From the `kudu` CLI tool:
{noformat}
$ ./bin/kudu table statistics 10.17.240.17:9876  
default.loadgen_auto_0867c7e10d894cabbe5536507b80b9d1
TABLE default.loadgen_auto_0867c7e10d894cabbe5536507b80b9d1
on disk size: 0
live row count: 0
{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: CLI, 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)

Reply via email to