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

rmetzger pushed a commit to branch release-1.13
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/release-1.13 by this push:
     new 6634b3f  [FLINK-23129][docs] Document ApplicationMode limitations
6634b3f is described below

commit 6634b3fc4ef7305513cef067b15edc3d4fa61e7f
Author: Robert Metzger <rmetz...@apache.org>
AuthorDate: Thu Jun 24 15:12:55 2021 +0200

    [FLINK-23129][docs] Document ApplicationMode limitations
    
    This closes #16281
---
 docs/content.zh/docs/deployment/overview.md | 4 ++++
 docs/content/docs/deployment/overview.md    | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/docs/content.zh/docs/deployment/overview.md 
b/docs/content.zh/docs/deployment/overview.md
index 960db9b..649d07d 100644
--- a/docs/content.zh/docs/deployment/overview.md
+++ b/docs/content.zh/docs/deployment/overview.md
@@ -205,6 +205,10 @@ non-blocking, will lead to the "next" job starting before 
"this" job finishes.
 The Application Mode allows for multi-`execute()` applications but 
 High-Availability is not supported in these cases. High-Availability in 
Application Mode is only
 supported for single-`execute()` applications.
+
+Additionally, when any of multiple running jobs in Application Mode (submitted 
for example using 
+`executeAsync()`) gets cancelled, all jobs will be stopped and the JobManager 
will shut down. 
+Regular job completions (by the sources shutting down) are supported.
 {{< /hint >}}
 
 #### Per-Job Mode
diff --git a/docs/content/docs/deployment/overview.md 
b/docs/content/docs/deployment/overview.md
index 85452b8..32d7348 100644
--- a/docs/content/docs/deployment/overview.md
+++ b/docs/content/docs/deployment/overview.md
@@ -205,6 +205,10 @@ non-blocking, will lead to the "next" job starting before 
"this" job finishes.
 The Application Mode allows for multi-`execute()` applications but 
 High-Availability is not supported in these cases. High-Availability in 
Application Mode is only
 supported for single-`execute()` applications.
+
+Additionally, when any of multiple running jobs in Application Mode (submitted 
for example using 
+`executeAsync()`) gets cancelled, all jobs will be stopped and the JobManager 
will shut down. 
+Regular job completions (by the sources shutting down) are supported.
 {{< /hint >}}
 
 #### Per-Job Mode

Reply via email to