dmvk commented on a change in pull request #17678:
URL: https://github.com/apache/flink/pull/17678#discussion_r754896636
##########
File path: docs/content/docs/deployment/overview.md
##########
@@ -179,18 +179,21 @@ network bandwidth to download dependencies and ship
binaries to the cluster, and
`main()`. This problem can be more pronounced when the Client is shared across
users.
Building on this observation, the *Application Mode* creates a cluster per
submitted application, but this time,
-the `main()` method of the application is executed on the JobManager. Creating
a cluster per application can be
+the `main()` method of the application is executed by the *JobManager*.
Creating a cluster per application can be
seen as creating a session cluster shared only among the jobs of a particular
application, and torn down when
the application finishes. With this architecture, the *Application Mode*
provides the same resource isolation
-and load balancing guarantees as the *Per-Job* mode, but at the granularity of
a whole application. Executing
-the `main()` on the JobManager allows for saving the CPU cycles required, but
also save the bandwidth required
-for downloading the dependencies locally. Furthermore, it allows for more even
spread of the network load for
-downloading the dependencies of the applications in the cluster, as there is
one JobManager per application.
+and load balancing guarantees as the *Per-Job* mode, but at the granularity of
a whole application.
+
+The *Application Mode* builds on an assumption that the user jars are already
available on the classpath (`usrlib` folder)
+of all Flink components that needs an access to it (*JobManager*,
*TaskManager*). In other words, your application comes
Review comment:
👍
--
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]
