[
https://issues.apache.org/jira/browse/FLINK-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977229#comment-16977229
]
Piotr Nowojski commented on FLINK-14814:
----------------------------------------
Ok, sounds good [~lining]. One thing:
> pool usage aggregated by max, min, and the average in every vertex for users
> to judge vertex
Do we need all of the aggregates? Max & min for example? Check my explanation
in FLINK-14815 for why I think min/max aggregate for pool usage might be
redundant to just average. On the other hand presenting too many metrics has
couple of potential issues:
# information spam to a user (why show him something that he doesn't need?)
# potential performance implications? Even if not now, but in the future, if we
add too many metrics now, it will be difficult to drop them in the future.
> 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: lining
> Priority: Major
> Attachments: 2B0E910D-6D95-401F-B450-1F6B1AFB9BEA.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)
