[
https://issues.apache.org/jira/browse/KUDU-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004870#comment-17004870
]
ASF subversion and git services commented on KUDU-3021:
-------------------------------------------------------
Commit e9656d0bcc060572be58b8248b3e14611ec79113 in kudu's branch
refs/heads/master from triplesheep
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=e9656d0 ]
KUDU-3021 Add metric for tablet transaction memory.
Currently we have 'transaction_memory_pressure_rejections' to
track the rejections for memory pressure, but it will also take
the limits of its ancestral memory trackers. Here add the
seperate metric to track just transaction-memory-limit-related
rejections.
Change-Id: I131b9ed27617274c1210a1678c1fdf7307b7edcc
Reviewed-on: http://gerrit.cloudera.org:8080/14911
Reviewed-by: Adar Dembo <a...@cloudera.com>
Tested-by: Adar Dembo <a...@cloudera.com>
> 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)
