XComp commented on a change in pull request #18910:
URL: https://github.com/apache/flink/pull/18910#discussion_r816067111
##########
File path: docs/content.zh/docs/deployment/overview.md
##########
@@ -152,7 +152,13 @@ When deploying Flink, there are often multiple options
available for each buildi
</tbody>
</table>
+### Repeatable Resource Cleanup Strategy
+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
based on
+a repeatable retry strategy. You can [configure]({{< ref
"docs/deployment/config#retryable-cleanup" >}}) this
Review comment:
```suggestion
failure when cleaning up a resource, Flink will attempt to retry the
cleanup. You can [configure]({{< ref "docs/deployment/config#retryable-cleanup"
>}}) this
```
##########
File path: docs/content.zh/docs/deployment/overview.md
##########
@@ -152,7 +152,13 @@ When deploying Flink, there are often multiple options
available for each buildi
</tbody>
</table>
+### Repeatable Resource Cleanup Strategy
Review comment:
```suggestion
### Repeatable Resource Cleanup
```
nit
##########
File path: docs/content.zh/docs/concepts/glossary.md
##########
@@ -78,6 +78,13 @@ A Flink Job is the runtime representation of a [logical
graph](#logical-graph)
见 [Logical Graph](#logical-graph)。
+#### JobResultStore
Review comment:
The `JobResultStore` should be located in front of the `Logical Graph`
entry because of the lexicographical order.
--
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]
