You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2015/09/17 20:27:05 UTC
[jira] [Resolved] (FLINK-2357) New JobManager Runtime Web Frontend
[ https://issues.apache.org/jira/browse/FLINK-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-2357.
---------------------------------
Resolution: Fixed
Assignee: Stephan Ewen
Fix Version/s: 0.10
Implemented in various commits by [~iampeter] and me. Merged as of 93a4d31d9e5d0ffa1ef2b578d1eee8088fa7c0e1
> New JobManager Runtime Web Frontend
> -----------------------------------
>
> Key: FLINK-2357
> URL: https://issues.apache.org/jira/browse/FLINK-2357
> Project: Flink
> Issue Type: New Feature
> Components: Webfrontend
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 0.10
>
> Attachments: Webfrontend Mockup.pdf
>
>
> We need to improve rework the Job Manager Web Frontend.
> The current web frontend is limited and has a lot of design issues
> - It does not display and progress while operators are running. This is especially problematic for streaming jobs
> - It has no graph representation of the data flows
> - it does not allow to look into execution attempts
> - it has no hook to deal with the upcoming live accumulators
> - The architecture is not very modular/extensible
> I propose to add a new JobManager web frontend:
> - Based on Netty HTTP (very lightweight)
> - Using rest-style URLs for jobs and vertices
> - integrating the D3 graph renderer of the previews with the runtime monitor
> - with details on execution attempts
> - first class visualization of records processed and bytes processed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)