You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by ma...@apache.org on 2022/03/11 15:15:16 UTC
[flink] branch master updated: [FLINK-26388][docs] Adds information about missed out artifacts in repeatable cleanup with a reference to the FLINK issue
This is an automated email from the ASF dual-hosted git repository.
mapohl pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new 71c0ede [FLINK-26388][docs] Adds information about missed out artifacts in repeatable cleanup with a reference to the FLINK issue
71c0ede is described below
commit 71c0ede64aaff40247c2b69295dbcddc8fe1cf11
Author: Matthias Pohl <ma...@ververica.com>
AuthorDate: Fri Mar 11 11:47:53 2022 +0100
[FLINK-26388][docs] Adds information about missed out artifacts in repeatable cleanup with a reference to the FLINK issue
---
docs/content.zh/docs/deployment/overview.md | 5 +++++
docs/content/docs/deployment/overview.md | 5 +++++
2 files changed, 10 insertions(+)
diff --git a/docs/content.zh/docs/deployment/overview.md b/docs/content.zh/docs/deployment/overview.md
index 049a254..df6abea 100644
--- a/docs/content.zh/docs/deployment/overview.md
+++ b/docs/content.zh/docs/deployment/overview.md
@@ -159,6 +159,11 @@ external component resources associated with the job are then cleaned up. In the
failure when cleaning up a resource, Flink will attempt to retry the cleanup. You can
[configure]({{< ref "docs/deployment/config#retryable-cleanup" >}}) the retry strategy used.
+There is currently an issue with the cleanup of CompletedCheckpoints that failed to be deleted
+while subsuming them as part of the usual CompletedCheckpoint management. These artifacts are
+not covered by the repeatable cleanup, i.e. they have to be deleted manually, still. This is
+covered by [FLINK-26606](https://issues.apache.org/jira/browse/FLINK-26606).
+
## Deployment Modes
Flink can execute applications in one of three ways:
diff --git a/docs/content/docs/deployment/overview.md b/docs/content/docs/deployment/overview.md
index bd929b0..64bac26 100644
--- a/docs/content/docs/deployment/overview.md
+++ b/docs/content/docs/deployment/overview.md
@@ -160,6 +160,11 @@ external component resources associated with the job are then cleaned up. In the
failure when cleaning up a resource, Flink will attempt to retry the cleanup. You can
[configure]({{< ref "docs/deployment/config#retryable-cleanup" >}}) the retry strategy used.
+There is currently an issue with the cleanup of CompletedCheckpoints that failed to be deleted
+while subsuming them as part of the usual CompletedCheckpoint management. These artifacts are
+not covered by the repeatable cleanup, i.e. they have to be deleted manually, still. This is
+covered by [FLINK-26606](https://issues.apache.org/jira/browse/FLINK-26606).
+
## Deployment Modes
Flink can execute applications in one of three ways: