[
https://issues.apache.org/jira/browse/FLINK-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20724:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Create a http handler for aggregating metrics from whole job
> ------------------------------------------------------------
>
> Key: FLINK-20724
> URL: https://issues.apache.org/jira/browse/FLINK-20724
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Affects Versions: 1.13.0, 1.12.3
> Reporter: Piotr Nowojski
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> This is an optimisation idea.
> Create a similar http handler to {{AggregatingSubtasksMetricsHandler}}, but
> one that would aggregate metrics per task, from all of the job vertices. The
> new handler would only take {{JobID}} as a parameter. So that Web UI can in
> one RPC obtain {{max(isBackPressureRatio)}} /
> {{max(isCausingBackPressureRatio)}} per each task in the job graph.
> This is related to FLINK-14712, where we are invoking more REST calls to get
> the statistics per each task/node (in order to color the nodes based on the
> back pressure and busy times). With this new handler, WebUI could make a one
> REST call to get all the metrics it needs, instead of doing one REST call per
> every Task.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
