Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Thu, 18 Feb 2016 18:02:18 +0000 (UTC)
From: "Ufuk Celebi (JIRA)" <jira@apache.org>
To: dev@flink.apache.org
Message-ID: <JIRA.12940218.1455818488000.84913.1455818538165@Atlassian.JIRA>
In-Reply-To: <JIRA.12940218.1455818488000@Atlassian.JIRA>
References: <JIRA.12940218.1455818488000@Atlassian.JIRA>
 <JIRA.12940218.1455818488381@arcas>
Subject: [jira] [Created] (FLINK-3443) JobManager cancel and clear
 everything fails jobs instead of cancelling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ufuk Celebi created FLINK-3443:
----------------------------------

             Summary: JobManager cancel and clear everything fails jobs instead of cancelling
                 Key: FLINK-3443
                 URL: https://issues.apache.org/jira/browse/FLINK-3443
             Project: Flink
          Issue Type: Bug
          Components: Distributed Runtime
            Reporter: Ufuk Celebi
            Assignee: Ufuk Celebi


When the job manager is shut down, it calls {{cancelAndClearEverything}}. This method does not {{cancel}} the {{ExecutionGraph}} instances, but {{fail}}s them, which can lead to {{ExecutionGraph}} restart.

I've noticed this in tests, where old graph got into a loop of restarts.

What I don't understand is why the futures etc. are not cancelled when the executor service is shut down.


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