[
https://issues.apache.org/jira/browse/KUDU-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-3021:
--------------------------------
Description:
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 transaction applied. That can help
with pro-active tuning of a Kudu cluster to sustain a planned increase in
workload.
> Add metric gauges for the size of transactions applied and number of failed
> 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
> 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 transaction applied. 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)
