amazon web services - Mesos Chronos cluster design solution on EC2 instaces -

some guidance required building mesosphere solution on amazon ec2 servers.

for staging state of application thinking of launching master , slave on single instance plus slave on different instance. plus marathon , chronos frameworks on top of mesos master node.

marathon should responsible running http server on same instance, should serve access layer mesosphere api's.

chronos used run 1000s of simple bash script (execution time 1-5sec) each. (in part not sure if aggregation of jobs needed)

1. should run chronos via marathon, or launch service on master node? there difference?

2. any guidance/advice on current architecture design?

3. is there official support amazon run mesosphere in amazon cloud?

you can run single master mesos cluster on 2 hosts not ha there no need run 2 instances of except mesos-slave.

if want use 2 hosts , use mesos recommend following setup:

host1:

• zookeeper
• mesos-master
• mesos-slave
• marathon
• chronos

host2:

• mesos-slave

you need configure quorum number 1 , run cluster (no master election can happend way, if host1 dies, processes stop executing). in practice run 2 instances of zookeeper , mesos-master (i saw working setup that) in theory leader election might screw things because of quorum setup of 2 zookeeper nodes. advice use @ least 3 host (each host running zookeeper, mesos-master, mesos-slave, marathon , chronos, new host's need run mesos-slave). way can manage host down.

if want stick 2 host setup gave advice, ask if haven't answered something.

also don't know official amazon support mesos.