Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3C5A317226 for ; Thu, 17 Sep 2015 18:27:05 +0000 (UTC) Received: (qmail 54224 invoked by uid 500); 17 Sep 2015 18:27:05 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 54001 invoked by uid 500); 17 Sep 2015 18:27:05 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 53857 invoked by uid 99); 17 Sep 2015 18:27:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Sep 2015 18:27:05 +0000 Date: Thu, 17 Sep 2015 18:27:05 +0000 (UTC) From: "Stephan Ewen (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (FLINK-2357) New JobManager Runtime Web Frontend MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)