You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2019/08/15 04:37:00 UTC

[jira] [Resolved] (KUDU-2797) Implement table size metrics

     [ https://issues.apache.org/jira/browse/KUDU-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adar Dembo resolved KUDU-2797.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.11.0

Lifu merged a first cut in commit 0d48cad. It supports aggregating row count (from LEADERs) and on-disk size into table-scoped entities on the master.

Future work could include:
* Additional metrics, such as tablet or tserver load characteristics.
* Exposing the aggregates via API for query planners.

> Implement table size metrics
> ----------------------------
>
>                 Key: KUDU-2797
>                 URL: https://issues.apache.org/jira/browse/KUDU-2797
>             Project: Kudu
>          Issue Type: Task
>          Components: master, metrics
>    Affects Versions: 1.8.0
>            Reporter: Mike Percy
>            Assignee: HeLifu
>            Priority: Major
>             Fix For: 1.11.0
>
>
> It would be valuable to implement table size metrics for row count and byte size (pre-replication and post-replication). The master could aggregate these stats from the various partitions (tablets) and expose aggregated metrics for consumption by monitoring systems and dashboards. These same metrics would also be valuable to display on the web UI.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)