[ 
https://issues.apache.org/jira/browse/FLINK-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632974#comment-15632974
 ] 

ASF GitHub Bot commented on FLINK-5007:
---------------------------------------

GitHub user uce opened a pull request:

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

    [FLINK-5007] [checkpointing] Retain externalized checkpoint on suspension

    Handles graceful cluster shut down (non-HA) like cancellation and respects 
the configured clean up behaviour.
    
    ```
    ExternalizedCheckpointCleanup.DELETE_ON_CANCELLATION => delete on suspension
    
    ExternalizedCheckpointCleanup.RETAIN_ON_CANCELLATION => retain on suspension
    ```

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

    $ git pull https://github.com/uce/flink 5007-suspend_external

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

    https://github.com/apache/flink/pull/2750.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 #2750
    
----
commit 9f422c23c0e99259f39c84c292d034d70d8078cb
Author: Ufuk Celebi <u...@apache.org>
Date:   2016-11-03T14:52:24Z

    [FLINK-5007] [checkpointing] Retain externalized checkpoint on suspension
    
    Handles graceful cluster shut down (non-HA) like cancellation.

----


> Retain externalized checkpoint on suspension
> --------------------------------------------
>
>                 Key: FLINK-5007
>                 URL: https://issues.apache.org/jira/browse/FLINK-5007
>             Project: Flink
>          Issue Type: Bug
>          Components: State Backends, Checkpointing
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>             Fix For: 1.2.0
>
>
> Externalized checkpoints are cleaned up when the job is suspended. 
> Suspensions happen on graceful shut down (non-HA) or loss of leadership (HA).
> In case of HA, the checkpoint store does not clean up any checkpoints as they 
> might be recovered by a new leader. The only way to stop a HA job is to 
> actually cancel it. Therefore the configured clean up behaviour doesn't 
> matter.
> In case of non-HA, suspensions happen because of graceful shut down (for 
> example stopping a YARN session). In this case I would treat the clean up 
> behaviour similar to cancelling the job.
> {code}
> ExternalizedCheckpointCleanup.DELETE_ON_CANCELLATION => delete on suspension
> ExternalizedCheckpointCleanup.RETAIN_ON_CANCELLATION => retain on suspension
> {code}



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

Reply via email to