You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "ZhangYao (Jira)" <ji...@apache.org> on 2019/12/15 16:13:00 UTC
[jira] [Assigned] (KUDU-3021) Add metric gauges for the size of
transactions applied to tablets and number of rejected transactions due to
their size
[ https://issues.apache.org/jira/browse/KUDU-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ZhangYao reassigned KUDU-3021:
------------------------------
Assignee: ZhangYao
> Add metric gauges for the size of transactions applied to tablets and number of rejected transactions due to their size
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: KUDU-3021
> URL: https://issues.apache.org/jira/browse/KUDU-3021
> Project: Kudu
> Issue Type: Improvement
> Components: master, tserver
> Reporter: Alexey Serbin
> Assignee: ZhangYao
> Priority: Major
> Labels: observability, scalability, troubleshooting
>
> Kudu servers have a limit on the size of transaction applied to a tablet: {{\-\-tablet_transaction_memory}}
> It would be nice to introduce corresponding metrics to gauge how relevant the current setting is for the actual size of transactions applied in a running Kudu cluster. That can help with pro-active tuning of a Kudu cluster to sustain a planned increase in workload.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)