[
https://issues.apache.org/jira/browse/FLINK-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336571#comment-17336571
]
Flink Jira Bot commented on FLINK-10452:
----------------------------------------
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> 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
> Labels: stale-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)
