Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

and

...

Docker

...

Container

...

with

...

Apache

...

Ignite

...

for

...

Task.

Goal Scenario

User

...

starts

...

Ignite

...

Mesos

...

Framework,

...

framework

...

scheduler

...

is

...

started

...

and

...

registers

...

with

...

the

...

Mesos

...

Master.

...

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

...

in

...

ignite-857

...

branch.
2.

...

Run

...

IgniteFramework
java

...

-cp

...

ignite-mesos-1.0.0-snapshot-jar-with-dependencies.jar

...

org.apache.ignite.messo.IgniteFramework

...

<mesos

...

master>:<mesos

...

port>

Resources

1.

...

Docker

...

container

...

https://registry.hub.docker.com/u/apacheignite/ignite-docker/
2.

...

JIRA

...

https://issues.apache.org/jira/browse/IGNITE-857