You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sagar Rao (Jira)" <ji...@apache.org> on 2022/01/28 02:14:00 UTC
[jira] [Updated] (KAFKA-13624) Add Metric for Store Cache Size
[ https://issues.apache.org/jira/browse/KAFKA-13624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sagar Rao updated KAFKA-13624:
------------------------------
Description: KIP-770 introduced a new metric called `{*}input-buffer-bytes-total`{*} to track the total amount of bytes accumulated by a task. While working through it's PR, it was suggested to add a similar metric for *cache-size-bytes-total* to track the cache size in bytes for a task. (was: The current config "buffered.records.per.partition" controls how many records in maximum to bookkeep, and hence it is exceed we would pause fetching from this partition. However this config has two issues:
* It's a per-partition config, so the total memory consumed is dependent on the dynamic number of partitions assigned.
* Record size could vary from case to case.
And hence it's hard to bound the memory usage for this buffering. We should consider deprecating that config with a global, e.g. "input.buffer.max.bytes" which controls how much bytes in total is allowed to be buffered. This is doable since we buffer the raw records in <byte[], byte[]>.)
> Add Metric for Store Cache Size
> -------------------------------
>
> Key: KAFKA-13624
> URL: https://issues.apache.org/jira/browse/KAFKA-13624
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Sagar Rao
> Assignee: Sagar Rao
> Priority: Major
> Labels: needs-kip
>
> KIP-770 introduced a new metric called `{*}input-buffer-bytes-total`{*} to track the total amount of bytes accumulated by a task. While working through it's PR, it was suggested to add a similar metric for *cache-size-bytes-total* to track the cache size in bytes for a task.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)