zentol commented on a change in pull request #19102:
URL: https://github.com/apache/flink/pull/19102#discussion_r827874011
##########
File path: docs/content.zh/docs/deployment/overview.md
##########
@@ -158,6 +158,11 @@ Once a job has reached a globally terminal state of either
finished, failed or c
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.
+Reaching the maximum number of retries without succeeding will leave the job
in a dirty state.
+Its artifacts would need to be cleaned up manually (see the
+[High Availability Services / JobResultStore]({{< ref
"docs/deployment/ha/overview#jobresultstore" >}})
+section for further details). Restarting the very same job (i.e. using the same
+job ID) will result in the cleanup being restarted again without running the
job again.
Review comment:
```suggestion
job ID) will result in the cleanup being restarted without running the job
again.
```
--
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]
