From 1104b4bc6f88925a77a9b1b059392a50f1abf1db Mon Sep 17 00:00:00 2001 From: Harshini Rangaswamy Date: Fri, 19 Jan 2024 14:37:36 +0100 Subject: [PATCH] updated sentence --- docs/products/flink/howto/restart-strategy-jar-applications.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/products/flink/howto/restart-strategy-jar-applications.rst b/docs/products/flink/howto/restart-strategy-jar-applications.rst index 434be51eb..b82f58bc7 100644 --- a/docs/products/flink/howto/restart-strategy-jar-applications.rst +++ b/docs/products/flink/howto/restart-strategy-jar-applications.rst @@ -38,7 +38,7 @@ Key considerations when disabling default restarts Before choosing to disable the default restart strategy, consider the following: -- **Persistent failures**: Disabling restarts means that if a Flink Job fails, Flink will not attempt to recover the job, leading to permanent job failure. +- **Persistent failures**: Disabling restarts means that if a Flink Job fails, Flink will not attempt to recover it, leading to permanent job failure. - **Testing and debugging**: Disabling is beneficial when identifying issues in the application code, as it prevents the masking of errors through automatic restarts. - **External factors**: Jobs can fail due to external factors, such as infrastructure changes or maintenance activities. If you disable restarts, your Flink jobs will become vulnerable to failures. - **Operational risks**: In production environments, it is generally advisable to use the default restart strategy to ensure high availability and fault tolerance.