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 4D46217B9A for ; Mon, 15 Jun 2015 14:39:02 +0000 (UTC) Received: (qmail 87150 invoked by uid 500); 15 Jun 2015 14:39:02 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 87059 invoked by uid 500); 15 Jun 2015 14:39:02 -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 86895 invoked by uid 99); 15 Jun 2015 14:39:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2015 14:39:02 +0000 Date: Mon, 15 Jun 2015 14:39:02 +0000 (UTC) From: "Till Rohrmann (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FLINK-2224) JobManager log does not contain root cause and stack trace of exceptions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Till Rohrmann created FLINK-2224: ------------------------------------ Summary: JobManager log does not contain root cause and stack trace of exceptions Key: FLINK-2224 URL: https://issues.apache.org/jira/browse/FLINK-2224 Project: Flink Issue Type: Bug Components: Core Reporter: Till Rohrmann While running cluster tests with failing jobs I noticed that the JobManager log file does neither contain the root cause of the failure nor a stack trace of it. The error was not sufficient resources available for scheduling. For the purpose of debugging, it is crucial to have this information in the log file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)