flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tillrohrmann <...@git.apache.org>
Subject [GitHub] flink pull request #2096: [FLINK-3800] [runtime] Introduce SUSPENDED job sta...
Date Mon, 13 Jun 2016 13:34:24 GMT
GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/2096

    [FLINK-3800] [runtime] Introduce SUSPENDED job status

    The SUSPENDED job status is a new ExecutionGraph state which can be reached from all
    non-terminal states when calling suspend on the ExecutionGraph. Unlike the FAILED,
    FINISHED and CANCELED state, the SUSPENDED state does not trigger the deletion of the
    job from the HA storage. Therefore, this state can be used to handle the loss of
    leadership or the shutdown of a JobManager so that the ExecutionGraph is stopped but
    can still be recovered. SUSPENDED is also a terminal state but it can be differentiated
as
    a locally terminal state from FAILED, CANCELED and FINISHED which are globally
    terminal states.
    
    Add test case for suspend signal
    
    Add test case for suspending restarting job
    
    Add test case for HA job recovery when losing leadership
    
    Add online documentation for the job status

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink fixHALifecycle

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2096.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2096
    
----
commit 0d3c738e85fed2e161bc724887a4d8ce06a2798c
Author: Till Rohrmann <trohrmann@apache.org>
Date:   2016-06-09T09:37:14Z

    [FLINK-3800] [runtime] Introduce SUSPENDED job status
    
    The SUSPENDED job status is a new ExecutionGraph state which can be reached from all
    non-terminal states when calling suspend on the ExecutionGraph. Unlike the FAILED,
    FINISHED and CANCELED state, the SUSPENDED state does not trigger the deletion of the
    job from the HA storage. Therefore, this state can be used to handle the loss of
    leadership or the shutdown of a JobManager so that the ExecutionGraph is stopped but
    can still be recovered. SUSPENDED is also a terminal state but it can be differentiated
as
    a locally terminal state from FAILED, CANCELED and FINISHED which are globally
    terminal states.
    
    Add test case for suspend signal
    
    Add test case for suspending restarting job
    
    Add test case for HA job recovery when losing leadership
    
    Add online documentation for the job status

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message