Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Mon, 31 Oct 2016 13:59:58 +0000 (UTC)
From: "Chesnay Schepler (JIRA)" <jira@apache.org>
To: dev@flink.apache.org
Message-ID: <JIRA.13016607.1477922377000.132577.1477922398763@Atlassian.JIRA>
In-Reply-To: <JIRA.13016607.1477922377000@Atlassian.JIRA>
References: <JIRA.13016607.1477922377000@Atlassian.JIRA> <JIRA.13016607.1477922377242@arcas>
Subject: [jira] [Created] (FLINK-4972) CoordinatorShutdownTestrelies on race
 for success
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 31 Oct 2016 14:00:00 -0000

Chesnay Schepler created FLINK-4972:
---------------------------------------

             Summary: CoordinatorShutdownTestrelies on race for success
                 Key: FLINK-4972
                 URL: https://issues.apache.org/jira/browse/FLINK-4972
             Project: Flink
          Issue Type: Improvement
          Components: Tests
    Affects Versions: 1.2.0
            Reporter: Chesnay Schepler
            Assignee: Chesnay Schepler
             Fix For: 1.2.0


The CoordinatorShutdownTest verifies that the CheckpointCoordinator is properly shutdown when a job has succeeded/failed. For this purpose a job is submitted to a cluster without TaskManagers, resulting in immediate failure. The ExecutionGraph is then retrieved, from which the CheckpointCoordinator can be accessed.

This test relies on being able to access the ExecutionGraph for a finished job even though it is only accessible for a short amount of time: until it was archived and removed from the currentJobs map in the JM. From that point on you can only retrieve an ArchivedExecutionGraph, which doesn't contain the CheckpointCoordinator anymore.

The tests should be changed to block the job execution, retrieve the ExecutionGraph, resume the job and then verify the test conditions.


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