This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.
Apache Mesos Framework support scheduling and running Apache Ignite nodes in a Mesos cluster. This develop a Mesos Scheduler, a Mesos Task.
User starts Ignite Mesos Framework, framework scheduler is started and registers in the Mesos Cluster. Once registration is successful the framework will start to launch tasks on nodes. The framework will begin expanding the cluster to the desired total number of nodes. If a node were to be lost, the framework would first attempt to restart the node and the framework will remove the lost node from the cluster.
Multiple instances of the framework can be run for multiple topology Frameworks will re-register with Mesos. Fault Tolerant, to restart failed Apache Ignite node tasks.
The Mesos scheduler is the component with the most high-level intelligence in the framework. It will need to possess the ability to start Apache Ignite cluster and distribute the correct configuration and packages to all started nodes.
The Mesos Task will be responsible for running container with required configuration.
For running Ignite Framework requires started Apache Mesos Cluster. Instruction how setting up a cluster: https://docs.mesosphere.com/getting-started/datacenter/install/.
Currently the recommended way to run the Ignite Framework is via Marathon.
Download or copy the json properties. Update the
MESOS_MASTER_URL and any other parameters which would like to change. See Properties section.
POST the config to Marathon by CURL or other tools.
curl -X POST -H "Content-type: application/json" --data-binary @marathon.json http://<marathon-ip>:8080/v2/apps/
Make sure thath Ignite cluster is running, for this:
Open Marathon UI at
http://<marathon-ip>:8080. Make sure that exists application with name
java -jar ignite-mesos-1.0.0-snapshot-jar-with-dependencies.jar
Make sure that Ignite cluster is running, for this:
3. Open Mesos console at
http://<master-ip>:5050. If all work correctly tasks with
"Ignite node N" should have state
"RUNNING" or "
4. Go to
5. Look at
The following properties can be used to configure the framework. The properties can be passed to how property of file or environment variables.
|The number of CPU Cores for each Apache Ignite node.|
|The number of Megabytes of RAM for each Apache Ignite node.|
|The number of Megabytes of Disk for each Apache Ignite node.|
|The number of nodes in the cluster.|
|The number of CPU Cores for Ignite cluster.|
|The number of Megabytes of RAM for Ignite cluster.|
|The number of Megabytes of Disk for each Apache Ignite cluster.|
|The minimum number of CPU cores required to run Apache Ignite node.|
|The minimum number of Megabytes of RAM cores required to run Apache Ignite node.|
|The version ignite which will be run on nodes.|
|The directory which will be used for saving.|
|The path to Apache Ignite config file.||N/A|
|The path to libs which will be added to classpath.||N/A|
|Mesos ZooKeeper URL to locate leading master.|