flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-4972) CoordinatorShutdownTest relies on race condition for success
Date Mon, 31 Oct 2016 15:10:58 GMT

     [ https://issues.apache.org/jira/browse/FLINK-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chesnay Schepler closed FLINK-4972.
    Resolution: Fixed

Fixed in 99f1dc3e24ec529852ce38bcb9c46ffaf749333d

> CoordinatorShutdownTest relies on race condition 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 with(out)
TaskManagers, resulting in a successful/failed job. 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.
> A failure of this test for this very reason was observed in https://github.com/apache/flink/pull/2616.

This message was sent by Atlassian JIRA

View raw message