[
https://issues.apache.org/jira/browse/FLINK-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256927#comment-17256927
]
Piotr Nowojski commented on FLINK-14814:
----------------------------------------
Previous approach using {{isBackPressuredRatio}} and
{{isCausingBackPressureRatio}} had a major problem with accuracy of
measurements, if load spikes were happening quicker/faster then the sampling
rate (it's impossible to accurately sample a wave, with sampling rate smaller
then half of the wave's frequency).
Because of that I switched to another approach: using
{{backPressuredTimeMsPerSecond}} and {{busyTimeMsPerSecond}} which we can
calculate much more accurately.
> Show the vertex that produces the backpressure source in the job
> ----------------------------------------------------------------
>
> Key: FLINK-14814
> URL: https://issues.apache.org/jira/browse/FLINK-14814
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics, Runtime / Network, Runtime / REST,
> Runtime / Web Frontend
> Reporter: lining
> Assignee: Piotr Nowojski
> Priority: Major
> Labels: pull-request-available
> Attachments: 2B0E910D-6D95-401F-B450-1F6B1AFB9BEA.png, Screenshot
> 2020-12-30 at 14.09.19.png, Screenshot 2020-12-31 at 10.27.52.png
>
>
> By checking the status of output and input buffer pools exposed via
> FLINK-14815 (output buffer empty, input buffer full) it is possible to
> display which node is a source of the back pressure. This information could
> be displayed/accessible in the Web Frontend.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
