October 2018
Intermediate to advanced
248 pages
4h 46m
English
This is a desirable Marathon feature: when one of the Marathon servers stop, another Marathon server takes over and makes up for the loss to keep the processes running.
To see the magic happen, you will first need to stop the marathon1 service—we have covered how to stop a service previously in this chapter while configuring the mesos-master. Once this is done, go to the Mesos console, and check the difference.
Hence, we have now seen how components support each other in an architecture.
Read now
Unlock full access