This is an automated email from the ASF dual-hosted git repository. roman pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/flink.git
commit 9e6d5520af4dde14ea7d5176f38856d90ac3d65d Author: Roman Khachatryan <[email protected]> AuthorDate: Fri Jul 22 14:05:24 2022 +0200 [hotfix][docs] Remove limitation about CLAIM mode and RocksDB native savepoints --- docs/content/docs/ops/state/savepoints.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/content/docs/ops/state/savepoints.md b/docs/content/docs/ops/state/savepoints.md index c7f80747340..c08587ec178 100644 --- a/docs/content/docs/ops/state/savepoints.md +++ b/docs/content/docs/ops/state/savepoints.md @@ -255,10 +255,8 @@ of the old job will not be deleted by Flink 2. [Native](#savepoint-format) format supports incremental RocksDB savepoints. For those savepoints Flink puts all SST files inside the savepoints directory. This means such savepoints are self-contained and relocatable. -However, when restored in CLAIM mode, subsequent checkpoints might reuse some SST files, which -in turn might block deleting the savepoints directory at the time the savepoint is subsumed. Later -on Flink will delete the reused shared SST files, but it won't retry deleting the savepoints directory. -Therefore, it is possible Flink leaves an empty savepoints directory if it was restored in CLAIM mode. +Please note that, when restored in CLAIM mode, subsequent checkpoints might reuse some SST files, which +might delay the deletion the savepoints directory. {{< /hint >}} **LEGACY**
