[
https://issues.apache.org/jira/browse/FLINK-21736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363360#comment-17363360
]
Yun Tang commented on FLINK-21736:
----------------------------------
[~trohrmann], sure.
https://issues.apache.org/jira/browse/FLINK-22528 already track this feature,
and I will prepare PR recently.
> 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)
