You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/03 13:06:00 UTC
[jira] [Updated] (KUDU-2643) Add tools to do basic analysis on the
metrics logs
[ https://issues.apache.org/jira/browse/KUDU-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-2643:
------------------------------
Target Version/s: (was: 1.9.0)
> Add tools to do basic analysis on the metrics logs
> --------------------------------------------------
>
> Key: KUDU-2643
> URL: https://issues.apache.org/jira/browse/KUDU-2643
> Project: Kudu
> Issue Type: Improvement
> Affects Versions: 1.8.0
> Reporter: William Berkeley
> Assignee: William Berkeley
> Priority: Major
>
> KUDU-2597 tracks adding a tool to parse the metrics logs. We should also add (probably as Python scripts) some tools for analyzing the metrics logs:
> * Finding tablets with unusual performance characteristics: longest apply|prepare|replicate|write|updateconsensus times
> * Finding servers with the most disk activity
> * Finding servers with slows scanners
> * Finding replicas that are largest on disk or in-memory
> * Characterizing workloads of tables and tablets (insert/upserts/deletes/updates/duplicate key inserts/pk lookups + times/op)
> * Compaction (average height, delta size, compaction times)
> * Log performance (append latency, sync latency, throughput)
> Some of this can be rules-based, i.e. if metric X is > constant A) and some should be pattern-based (most tablets' histograms look different than this tablet's).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)