pnowojski opened a new pull request #18181:
URL: https://github.com/apache/flink/pull/18181
Currently back pressured/busy metrics tell the user whether task is
blocked/busy and how much % of the time it is blocked/busy. But they do not
tell how for how long single block event is lasting. It can be 1ms or 1h and
back pressure/busy would be still reporting 100%.
In order to improve this, we could provide two new metrics:
`maxSoftBackPressureTime`
`maxHardBackPressureTime`
The max would be reset to 0 periodically or on every access to the metric
(via metric reporter). Soft back pressure would be if task is back pressured in
a non blocking fashion (StreamTask detected in availability of the output).
Hard back pressure would measure the time task is actually blocked.
In order to calculate those metrics I'm proposing to split the already
existing `backPressuredTimeMsPerSecond` into soft and hard versions as well.
## Brief change log
Please check the individual commits.
## Verifying this change
This PR adds a couple of new assertions in the existing unit tests and
additionally I have manually verified the changes in the WebUI.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no**
/ don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / **no** / don't
know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (**yes** / no)
- If yes, how is the feature documented? (not applicable / **docs** /
JavaDocs / not documented)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
