[
https://issues.apache.org/jira/browse/KUDU-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995441#comment-16995441
]
ZhangYao commented on KUDU-3021:
--------------------------------
We already have {color:#172b4d}*_transaction_memory_pressure_rejections_* in
TransactionTracker. It will track the rejection of transactions for memory
reason. But we will check the whole memory track tree for consumption capacity,
so this metrics not only decided by *_--tablet_transaction_memory_* but also
its parents. So do we want exactly metrics for the setting of
*_tablet_transaction_memory_* or *_transaction_memory_pressure_rejections_* is
enough? :){color}
> 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
> 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)
