[KUDU-3021] Add metric gauges for the size of transactions applied to tablets and number of rejected transactions due to their size

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: master, metrics, tserver
• Labels: observability scalability troubleshooting
• Assignee: ZhangYao
• Reporter: Alexey Serbin
• Created: 13/Dec/19 03:40
• Updated: 03/Jun/20 15:57

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 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.