[
https://issues.apache.org/jira/browse/FLINK-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711185#comment-16711185
]
vinoyang commented on FLINK-10452:
----------------------------------
I will agree with [~stevenz3wu] to count the total number of keys, which will
make a lot of sense for monitoring. It is not easy to count the state size in
the keyed state backend, and the overhead is relatively large. What do you
think? [~Zentol] [~srichter]
> 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: Metrics
> Reporter: Konstantin Knauf
> Assignee: vinoyang
> 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
(v7.6.3#76005)
