[jira] [Commented] (FLINK-1579) Create a Flink History Server

["Stephan Ewen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239790#comment-15239790 ] 

Stephan Ewen commented on FLINK-1579:
-------------------------------------

The good thing in the current design is that all data (after the job is done) is simply JSON objects behind static REST-style URLs.
All dynamic logic is client-side, in the browser.

A simple server that the JobManager could push the JSON to (under the URLs) should actually do most of the job.
That would, however, not cover authentication, and result in separate services for live and historic jobs.

> Create a Flink History Server
> -----------------------------
>
>                 Key: FLINK-1579
>                 URL: https://issues.apache.org/jira/browse/FLINK-1579
>             Project: Flink
>          Issue Type: New Feature
>    Affects Versions: 0.9
>            Reporter: Robert Metzger
>
> Right now its not possible to analyze the job results for jobs that ran on YARN, because we'll loose the information once the JobManager has stopped.
> Therefore, I propose to implement a "Flink History Server" which serves  the results from these jobs.
> I haven't started thinking about the implementation, but I suspect it involves some JSON files stored in HDFS :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)