XComp commented on a change in pull request #19102:
URL: https://github.com/apache/flink/pull/19102#discussion_r827372013
##########
File path: docs/content/docs/deployment/overview.md
##########
@@ -158,7 +158,12 @@ When deploying Flink, there are often multiple options
available for each buildi
Once a job has reached a globally terminal state of either finished, failed or
cancelled, the
external component resources associated with the job are then cleaned up. In
the event of a
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.
+[configure]({{< ref "docs/deployment/config#retryable-cleanup" >}}) the retry
strategy used.
+Reaching the maximum number of retries without succeeding will leave the job
in a dirty state.
Review comment:
I updated the documentation under `Deployment / High Availability /
Overview / JobResultStore` to also cover dirty entries with references to the
folders.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
