Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.19.0
Description
Currently there is no way of knowing how many timers are being fired by Flink, so it's impossible to distinguish, even using code profiling, if operator is firing only a couple of heavy timers per second using ~100% of the CPU time, vs firing thousands of timer per seconds.
We could add the following metrics to address this issue:
- numFiredTimers - total number of fired timers per operator
- numFiredTimersPerSecond - per second rate of firing timers per operator
Attachments
Attachments
Issue Links
- is related to
-
FLINK-32954 Metrics expose number of heap timer
- Open
- links to