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

Posted to issues@flink.apache.org by "Monal Daxini (JIRA)" <ji...@apache.org> on 2018/09/25 20:16:00 UTC

[jira] [Comment Edited] (FLINK-10423) Forward RocksDB memory metrics to Flink metrics reporter

    [ https://issues.apache.org/jira/browse/FLINK-10423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627866#comment-16627866 ] 

Monal Daxini edited comment on FLINK-10423 at 9/25/18 8:15 PM:
---------------------------------------------------------------

It will be great to have this ported to 1.6 release.

Spoke with [~srichter] about this offline.


was (Author: mdaxini):
It will be great to have this ported to 1.6 release as well. 

Spoke with [~srichter] about this offline.

> Forward RocksDB memory metrics to Flink metrics reporter 
> ---------------------------------------------------------
>
>                 Key: FLINK-10423
>                 URL: https://issues.apache.org/jira/browse/FLINK-10423
>             Project: Flink
>          Issue Type: New Feature
>          Components: Metrics, State Backends, Checkpointing
>            Reporter: Seth Wiesman
>            Assignee: Seth Wiesman
>            Priority: Major
>
> RocksDB contains a number of metrics at the column family level about current memory usage, open memtables,  etc that would be useful to users wishing greater insight what rocksdb is doing. This work is inspired heavily by the comments on this rocksdb issue thread (https://github.com/facebook/rocksdb/issues/3216#issuecomment-348779233)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)