Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Mon, 15 Jun 2015 09:33:01 +0000 (UTC)
From: "Ufuk Celebi (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12775869.1424265765000.70581.1434360781100@Atlassian.JIRA>
In-Reply-To: <JIRA.12775869.1424265765000@Atlassian.JIRA>
References: <JIRA.12775869.1424265765000@Atlassian.JIRA>
 <JIRA.12775869.1424265765678@arcas>
Subject: [jira] [Commented] (FLINK-1579) Create a Flink History Server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ufuk Celebi commented on FLINK-1579:
------------------------------------

Just to ping this issue again. Another user asked for this.

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