[
https://issues.apache.org/jira/browse/FLINK-10969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Zhen Wu updated FLINK-10969:
-----------------------------------
Description:
[~srichter] mentioned it might make sense to provide two versions: exact count
and approximate count. For some state backend (likes rocksDB), it may be much
cheaper to get approximate count.
exposing as metrics would be ideal.
Additionally, it will also be useful to get the total count of timers, which
are also stored in state backend. Stefan mentioned timers are just a different
namespace in state backend (e.g. column family in rocksDB). So it will be very
useful if the metrics have _namespace_ tag.
was:[~srichter] mentioned it might make sense to provide two versions: exact
count and approximate count. For some state backend (likes rocksDB), it may be
much cheaper to get approximate count.
> expose API or metric for total number of keys stored in state backend
> ---------------------------------------------------------------------
>
> Key: FLINK-10969
> URL: https://issues.apache.org/jira/browse/FLINK-10969
> Project: Flink
> Issue Type: New Feature
> Components: State Backends, Checkpointing
> Reporter: Steven Zhen Wu
> Priority: Major
>
> [~srichter] mentioned it might make sense to provide two versions: exact
> count and approximate count. For some state backend (likes rocksDB), it may
> be much cheaper to get approximate count.
> exposing as metrics would be ideal.
> Additionally, it will also be useful to get the total count of timers, which
> are also stored in state backend. Stefan mentioned timers are just a
> different namespace in state backend (e.g. column family in rocksDB). So it
> will be very useful if the metrics have _namespace_ tag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
