[
https://issues.apache.org/jira/browse/FLINK-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124267#comment-15124267
]
ASF GitHub Bot commented on FLINK-3160:
---------------------------------------
GitHub user greghogan opened a pull request:
https://github.com/apache/flink/pull/1564
[FLINK-3160] [web-dashboard] Aggregate operator statistics by TaskManager
Adds a new per-job tab displaying task statistics aggregated by TaskManager
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/greghogan/flink
3160_aggregate_operator_statistics_by_taskmanager
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1564.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1564
----
commit b5560010e6d1535b67d8077c418861c87518e803
Author: Greg Hogan <[email protected]>
Date: 2016-01-28T18:11:39Z
[FLINK-3160] [web-dashboard] Aggregate operator statistics by TaskManager
Adds a new per-job tab displaying task statistics aggregated by TaskManager
----
> 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)
