flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Zagrebin <and...@data-artisans.com>
Subject Re: TimerService Troubleshooting/Metrics
Date Tue, 18 Dec 2018 18:43:02 GMT
Hi Sayat,

As far as I know, there are no timer service metrics exposed at the moment.
I pull in Stefan into the thread, maybe, he could add more.

In case of RocksDB, you can try enabling RocksDB internal metrics [1].
Timer service uses RocksDB state backend to queue timers and has a dedicated column in RocksDB.
The metrics of this column might help, like 'state.backend.rocksdb.metrics.estimate-num-keys’.


[1] https://ci.apache.org/projects/flink/flink-docs-release-1.7/ops/config.html#rocksdb-native-metrics

> On 14 Dec 2018, at 16:01, sayat <stb.satybald@gmail.com> wrote:
> Dear Flink Community,
> Is there a way of troubleshooting timer service? In the docs, it says that the service
might degrade a job performance significantly. Is there a way how to expose and see timer
service metrics i.e. length of the priority queue, how many time the service fires etc?

View raw message