[flink] branch master updated: [FLINK-24090][docs] Added Troubleshooting section with ignoring in-flight data explanation into unaligned checkpoints page

[pn...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

pnowojski 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 5b47a81  [FLINK-24090][docs] Added Troubleshooting section with ignoring in-flight data explanation into unaligned checkpoints page
5b47a81 is described below

commit 5b47a815832cda1fa2fb210ae4247201a8baf01f
Author: Anton Kalashnikov <ka...@yandex.ru>
AuthorDate: Thu Sep 2 16:23:36 2021 +0200

    [FLINK-24090][docs] Added Troubleshooting section with ignoring in-flight data explanation into unaligned checkpoints page
---
 docs/content/docs/ops/state/unaligned_checkpoints.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/content/docs/ops/state/unaligned_checkpoints.md b/docs/content/docs/ops/state/unaligned_checkpoints.md
index b47e43e..591c838 100644
--- a/docs/content/docs/ops/state/unaligned_checkpoints.md
+++ b/docs/content/docs/ops/state/unaligned_checkpoints.md
@@ -118,3 +118,15 @@ operators. Flink implements the broadcast state by checkpointing only a single c
 from subtask 0 of the stateful operator. Upon restore, we send that copy to all of the
 operators. Therefore it might happen that an operator will get the state with changes applied for a
 record that it will soon consume from its checkpointed channels.
+
+## Troubleshooting
+
+### Corrupted in-flight data
+{{< hint warning >}}
+Actions described below are a last resort as they will lead to data loss.
+{{< /hint >}}
+In case of the in-flight data corrupted or by another reason when the job should be restored without the in-flight data, 
+it is possible to use  [recover-without-channel-state.checkpoint-id]({{< ref "docs/deployment/config" >}}#execution-checkpointing-recover-without-channel-state-checkpoint) property.
+This property requires to specify a checkpoint id for which in-flight data will be ignored.
+Do not set this property, unless a corruption inside the persisted in-flight data has lead to an otherwise unrecoverable situation.
+The property can be applied only after the job will be redeployed which means this operation makes sense only if [externalized checkpoint]({{< ref "docs/dev/datastream/fault-tolerance/checkpointing" >}}#enabling-and-configuring-checkpointing) is enabled.