Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Thu, 3 Nov 2016 14:46:59 +0000 (UTC)
From: "Ufuk Celebi (JIRA)" <jira@apache.org>
To: dev@flink.apache.org
Message-ID: <JIRA.13017662.1478184401000.173152.1478184419318@Atlassian.JIRA>
In-Reply-To: <JIRA.13017662.1478184401000@Atlassian.JIRA>
References: <JIRA.13017662.1478184401000@Atlassian.JIRA> <JIRA.13017662.1478184401612@arcas>
Subject: [jira] [Created] (FLINK-5007) Retain externalized checkpoint on
 suspension
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 03 Nov 2016 14:47:01 -0000

Ufuk Celebi created FLINK-5007:
----------------------------------

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