XComp commented on a change in pull request #14258:
URL: https://github.com/apache/flink/pull/14258#discussion_r538560185
##########
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
+on Mesos cluster.
-Flink's Mesos scheduler itself is currently not highly available. However, it
-persists all necessary information about its state (e.g. configuration, list of
-workers) in Zookeeper. In the presence of a failure, it relies on an external
-system to bring up a new scheduler. The scheduler will then register with Mesos
-again and go through the reconciliation phase. In the reconciliation phase, the
-scheduler receives a list of running workers nodes. It matches these against
the
-recovered information from Zookeeper and makes sure to bring back the cluster
in
-the state before the failure.
-### Artifact Server
+### Preparation
-The artifact server is responsible for providing resources to the worker
-nodes. The resources can be anything from the Flink binaries to shared secrets
-or configuration files. For instance, in non-containerized environments, the
-artifact server will provide the Flink binaries. What files will be served
-depends on the configuration overlay used.
+Flink on Mesos expects a Mesos cluster to be around. It also requires the
Flink binaries being deployed
+ontothe the Mesos master. Additionally, Hadoop needs to be installed on the
very same machine.
Review comment:
I verified it: Using the bundled jars would be another approach to
achieve it. I'm gonna add a Hadoop section similar to YARN's Hadoop sections.
----------------------------------------------------------------
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]
