Start your servicesΒΆ

When you install mesos, the master and slave services are enabled (called mesos-master and mesos-slave). Here, we want our master to focus on this tasks so we need to disable the slave service.

Do this on all the master nodes:

sudo systemctl stop mesos-slave
printf manual | sudo tee /etc/init/mesos-slave.override

We need to restart our zookeeper process and start mesos-master and marathon on all master nodes:

sudo systemctl restart zookeeper

sudo systemctl enable mesos-master

sudo systemctl start mesos-master

sudo systemctl enable marathon

sudo systemctl start marathon

We can validate that it works by connecting to mesos and marathon. Mesos runs on port 5050 (http) while marathon runs on port 8080.

Mesos:

../../_images/setup-master-check-UI-mesos-master.png

Marathon:

../../_images/setup-master-check-UI-marathon.png

if you want to check whether the service started as expected, you can use the following commands:

sudo systemctl status mesos-master

sudo systemctl status marathon

you should see something like this:

../../_images/setup-master-check-service-mesos-master.png ../../_images/setup-master-check-service-marathon.png

Check the about section in marathon to have the information about the service.

../../_images/setup-master-about-marathon.png
You can do the following to test the high availability of marathon:
  • Find on which mesos is running the framework marathon (here based on our screenshot above, it is available on master1)
  • Restart this master and you should see the framework was restarted automatically on another host
../../_images/setup-master-test-HA-marathon.png