[
https://issues.apache.org/jira/browse/FLINK-21736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Tang updated FLINK-21736:
-----------------------------
Release Note: State access latency metrics are introduced to track all
kinds of keyed state access to help debug state performance. This feature is
not enabled by default and could be turned on once setting
`state.backend.latency-track.keyed-state-enabled` as true.
> Introduce latency tracking state
> --------------------------------
>
> Key: FLINK-21736
> URL: https://issues.apache.org/jira/browse/FLINK-21736
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / State Backends
> Reporter: Yun Tang
> Assignee: Yun Tang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> This ticket is extended from FLINK-16444 which wants to track latency of
> RocksDB options. However previous ticket has two problems:
> # Cannot apply to heap based state backend and other user customized state
> backend.
> # User need background knowledge to know what RocksDB operation
> corresponding to what state operation, e.g RocksDB adopts {{merge}} to act as
> listState#add.
> Thus, I prefer to introduce latency tracking state wrapper to detect the
> access latency. And to not impact the original state access, I would still
> use sample interval as previous FLINK-16444 did.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
