You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/04/24 10:07:00 UTC

[jira] [Updated] (FLINK-10452) Expose Additional Metrics to Reason about Statesize

     [ https://issues.apache.org/jira/browse/FLINK-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-10452:
----------------------------------
    Component/s: Runtime / State Backends

> Expose Additional Metrics to Reason about Statesize
> ---------------------------------------------------
>
>                 Key: FLINK-10452
>                 URL: https://issues.apache.org/jira/browse/FLINK-10452
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics, Runtime / State Backends
>            Reporter: Konstantin Knauf
>            Priority: Major
>
> For monitoring purposes it would be helpful, if Flink could expose metrics about the number of keys/windows for each registered keyed state. 
> Open Questions:
> * One Metric per Registered State? One Metric per KeyedOperator?
> * Performance Impact (should this be default behavior?)
> * Possible to know the number of windows during runtime?
> * RocksDB only gives you an estimate of the number keys. Would be nice if we could derive the exact number inside Flink. This would also help in sizing the RocksDB instances and estimated their memory footprint.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)