[
https://issues.apache.org/jira/browse/FLINK-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10452:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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.20.1#820001)
