You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Greg Hogan (JIRA)" <ji...@apache.org> on 2015/12/17 23:18:46 UTC

[jira] [Assigned] (FLINK-3160) Aggregate operator statistics by TaskManager

     [ https://issues.apache.org/jira/browse/FLINK-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Greg Hogan reassigned FLINK-3160:
---------------------------------

    Assignee: Greg Hogan

> 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)