flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5007) Retain externalized checkpoint on suspension
Date Mon, 12 Dec 2016 16:42:58 GMT

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

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

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/2750
  
    Okay, understood, that makes sense.
    
    +1 from my side


> 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)

Mime
View raw message