[
https://issues.apache.org/jira/browse/KAFKA-17895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-17895:
------------------------------------
Description:
Tracking the evolution of a state store's size is often useful.
For example, we often use state store to persist pending work and set alert on
maximum size because it means the process is falling behind.
While KafkaStreams exposes many generic state store related or RocksDB
specificif metrics; is does not expose KeyValueStore#approximateNumEntries
which is a key information.
Is it an oversight or was it a deliberate choice?
I would be great if this metrics could be added. I assume that both in-memory &
rocksdb implementation of approximateNumEntries are fast enought to be used in
metrics.
KIP-1250:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-1250%3A+Add+metric+to+track+size+of+in-memory+state+stores]
was:
Tracking the evolution of a state store's size is often useful.
For example, we often use state store to persist pending work and set alert on
maximum size because it means the process is falling behind.
While KafkaStreams exposes many generic state store related or RocksDB
specificif metrics; is does not expose KeyValueStore#approximateNumEntries
which is a key information.
Is it an oversight or was it a deliberate choice?
I would be great if this metrics could be added. I assume that both in-memory &
rocksdb implementation of approximateNumEntries are fast enought to be used in
metrics.
> Expose KeyValueStore's approximateNumEntries as a metric
> --------------------------------------------------------
>
> Key: KAFKA-17895
> URL: https://issues.apache.org/jira/browse/KAFKA-17895
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 3.8.1
> Reporter: Clément MATHIEU
> Assignee: Evan Zhou
> Priority: Minor
> Labels: kip
>
> Tracking the evolution of a state store's size is often useful.
> For example, we often use state store to persist pending work and set alert
> on maximum size because it means the process is falling behind.
> While KafkaStreams exposes many generic state store related or RocksDB
> specificif metrics; is does not expose KeyValueStore#approximateNumEntries
> which is a key information.
> Is it an oversight or was it a deliberate choice?
> I would be great if this metrics could be added. I assume that both in-memory
> & rocksdb implementation of approximateNumEntries are fast enought to be used
> in metrics.
> KIP-1250:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-1250%3A+Add+metric+to+track+size+of+in-memory+state+stores]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
