THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Design
Apache Mesos Framework should support scheduling and running Apache Ignite nodes in a Mesos cluster. This would develop a Mesos Scheduler, a Mesos Task. Java will be used as the implementation language for the Framework Scheduler.
Goal Scenario
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 if unable to restart the node the framework would remove the lost node from the cluster.
Components
Mesos Framework
Multiple instances of the framework can be run for multiple topology Frameworks will re-register with Mesos when restarting if it was previously registered
Fault Tolerant, to restart failed Apache Ignite node tasks.
Mesos Scheduler
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 to all started nodes.
Responsibilities
- Restarting failed nodes
- Providing configuration to nodes (JVM OPTS)
- Auto scaling
Mesos Task
The Docker Mesos Task will be responsible for running container with required configuration.
How run Ignite Framework
1. Build ignite-mesos module.
2. Run IgniteFramework.
java -jar ignite-mesos-1.0.0-snapshot-jar-with-dependencies.jar [-cfg (path to config)]
Properties
The following properties can be used to configure the framework. The properties can be passed to how property of file or environment variables.
| name | description | default | example |
|---|---|---|---|
IGNITE_RUN_CPU_PER_NODE | The number of CPU Cores for each Apache Ignite node. | UNLIMITED | 2 |
IGNITE_MEMORY_PER_NODE | The number of Megabytes of RAM for each Apache Ignite node. | UNLIMITED | 1024 |
IGNITE_DISK_SPACE_PER_NODE | The number of Megabytes of Disk for each Apache Ignite node. | 1024 | 1024 |
IGNITE_NODE_COUNT | The number of nodes in the cluster. | 5 | 10 |
IGNITE_TOTAL_CPU | The number of CPU Cores for Ignite cluster. | UNLIMITED | 5 |
IGNITE_TOTAL_MEMORY | The number of Megabytes of RAM for Ignite cluster. | UNLIMITED | 16024 |
IGNITE_TOTAL_DISK_SPACE | The number of Megabytes of Disk for each Apache Ignite cluster. | UNLIMITED | 5024 |
IGNITE_MIN_CPU_PER_NODE | The minimum number of CPU cores required to run Apache Ignite node. | 1 | 4 |
IGNITE_MIN_MEMORY_PER_NODE | The minimum number of Megabytes of RAM cores required to run Apache Ignite node. | 256 | 1024 |
IGNITE_VERSION | The version ignite which will be run on nodes. | latest | 1.0.5 |
IGNITE_WORK_DIR | The directory which will be used for saving. | ignite-release | /opt/ignite/ |
IGNITE_XML_CONFIG | The path to Apache Ignite config file. | N/A | /opt/ignite/ignite-config.xml |
IGNITE_USERS_LIBS | The path to libs which will be added to classpath. | N/A | /opt/libs/ |
MESOS_MASTER_URL | Mesos ZooKeeper URL to locate leading master. | zk://localhost:2181/mesos | zk://176.0.1.45:2181/mesos or 176.0.1.45:2181 |
Resources
1. Docker container
2. JIRA
Overview
Content Tools
Apps
