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 DEB9218933 for ; Tue, 21 Jul 2015 18:18:04 +0000 (UTC) Received: (qmail 16316 invoked by uid 500); 21 Jul 2015 18:18:04 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 16271 invoked by uid 500); 21 Jul 2015 18:18:04 -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 16260 invoked by uid 99); 21 Jul 2015 18:18:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jul 2015 18:18:04 +0000 Date: Tue, 21 Jul 2015 18:18:04 +0000 (UTC) From: "Enrique Bautista Barahona (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLINK-2388) JobManager should try retrieving jobs from archive 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-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enrique Bautista Barahona updated FLINK-2388: --------------------------------------------- Description: I was following the quickstart guide with the WordCount example and, when I entered the "analyze" page for the job, nothing came up. Apparently the JobManagerInfoServlet fails with a NullPointerException. I've been reading the code and I've seen the problem is in the processing of the RequestAccumulatorResultsStringified message in JobManager. There's a TODO where the accumulators should be retrieved from the archive. As I wanted to know more about Flink internals, I decided to try and fix it. I've later seen that there's currently ongoing work in that part of the code, so I guess maybe it's not needed, but if you want I could submit a PR. If you have already taken it into account and will solve it shortly, please feel free to close the issue. was: I was following the quickstart guide with the WordCount example and, when I entered the "analyze" page for the job, nothing came up. Apparently the JobManagerInfoServlet fails with a NullPointerException. I've been reading the code and I've seen the problem is in the processing of the RequestAccumulatorResultsStringified message in JobManager. There's a TODO where the accumulators should be retrieved from the archive. As I wanted to know more about Flink internals, I decided to try and fix it. I've later seen that there's currently ongoing work in that part of the code, so I guess maybe it's not needed, but if you want I could submit a PR. If you have already taken it into account and will solve ti shortly, please feel free to close the issue. > JobManager should try retrieving jobs from archive > -------------------------------------------------- > > Key: FLINK-2388 > URL: https://issues.apache.org/jira/browse/FLINK-2388 > Project: Flink > Issue Type: Task > Components: JobManager > Reporter: Enrique Bautista Barahona > > I was following the quickstart guide with the WordCount example and, when I entered the "analyze" page for the job, nothing came up. Apparently the JobManagerInfoServlet fails with a NullPointerException. > I've been reading the code and I've seen the problem is in the processing of the RequestAccumulatorResultsStringified message in JobManager. There's a TODO where the accumulators should be retrieved from the archive. > As I wanted to know more about Flink internals, I decided to try and fix it. I've later seen that there's currently ongoing work in that part of the code, so I guess maybe it's not needed, but if you want I could submit a PR. If you have already taken it into account and will solve it shortly, please feel free to close the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)