You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Zakelly Lan (Jira)" <ji...@apache.org> on 2025/04/21 03:33:00 UTC

[jira] [Updated] (FLINK-34558) Add RocksDB key/value size metrics

     [ https://issues.apache.org/jira/browse/FLINK-34558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zakelly Lan updated FLINK-34558:
--------------------------------
    Fix Version/s: 2.1.0

> Add RocksDB key/value size metrics
> ----------------------------------
>
>                 Key: FLINK-34558
>                 URL: https://issues.apache.org/jira/browse/FLINK-34558
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>    Affects Versions: 2.0.0
>            Reporter: Jufang He
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.1.0
>
>
> In some scenarios, the poor performance of RocksDB may be caused by too large key/value size, but now there is a lack of metrics for key/value size. By adding these metrics, we can conveniently calculate the distribution of key/value size, such as the average size and p99 size.  To reduce the negative impact of adding metric on RocksDB performance, we could reduce the impact by supporting sampling.
> The possible implementation is as follows: After the RocksDB key/value serialization, we could obtain the byte array and report the size of the array through histogram metrics.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)