[
https://issues.apache.org/jira/browse/FLINK-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142601#comment-15142601
]
ASF GitHub Bot commented on FLINK-3160:
---------------------------------------
Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/1564#discussion_r52588713
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/ExecutionJobVertex.java
---
@@ -203,6 +204,27 @@ public JobVertexID getJobVertexId() {
public ExecutionVertex[] getTaskVertices() {
return taskVertices;
}
+
+ public Map<String, List<ExecutionVertex>>
getTaskVerticesByTaskManager() {
--- End diff --
Can we move this to the handler? I think that will be the only place where
we use it in the future as well.
> Aggregate operator statistics by TaskManager
> --------------------------------------------
>
> Key: FLINK-3160
> URL: https://issues.apache.org/jira/browse/FLINK-3160
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: 1.0.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
>
> The web client job info page presents a table of the following per task
> statistics: start time, end time, duration, bytes received, records received,
> bytes sent, records sent, attempt, host, status.
> Flink supports clusters with thousands of slots and a job setting a high
> parallelism renders this job info page unwieldy and difficult to analyze in
> real-time.
> It would be helpful to optionally or automatically aggregate statistics by
> TaskManager. These rows could then be expanded to reveal the current per task
> statistics.
> Start time, end time, duration, and attempt are not applicable to a
> TaskManager since new tasks for repeated attempts may be started. Bytes
> received, records received, bytes sent, and records sent are summed. Any
> throughput metrics can be averaged over the total task time or time window.
> Status could reference the number of running tasks on the TaskManager or an
> idle state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
