XComp commented on a change in pull request #14258:
URL: https://github.com/apache/flink/pull/14258#discussion_r538454237
##########
File path: docs/deployment/resource-providers/mesos.md
##########
@@ -26,226 +26,217 @@ under the License.
* This will be replaced by the TOC
{:toc}
-## Background
+## Getting Started
-The Mesos implementation consists of two components: The Application Master and
-the Worker. The workers are simple TaskManagers which are parameterized by the
environment
-set up by the application master. The most sophisticated component of the Mesos
-implementation is the application master. The application master currently
hosts
-the following components:
+This *Getting Started* section guides you through setting up a fully
functional Flink Cluster on Mesos.
-### Mesos Scheduler
+### Introduction
-The scheduler is responsible for registering the framework with Mesos,
-requesting resources, and launching worker nodes. The scheduler continuously
-needs to report back to Mesos to ensure the framework is in a healthy state. To
-verify the health of the cluster, the scheduler monitors the spawned workers
and
-marks them as failed and restarts them if necessary.
+[Apache Mesos](http://mesos.apache.org/) is another resource provider
supported by
+Apache Flink. Flink utilizes the worker's provided by Mesos to run its
TaskManagers.
+Apache Flink provides the script `bin/mesos-appmaster.sh` to create the Flink
Review comment:
Good that you mention that. I struggled to verify that firstly even
though the old docs mentioned it as well. Hence, I didn't add it in my version
of the docs.
But trying to run the script from an Mesos-independent instance worked now.
I adapted the docs to reflect it.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
