Book Image

Apache Mesos Cookbook

By : David Blomquist, Tomasz Janiszewski
Book Image

Apache Mesos Cookbook

By: David Blomquist, Tomasz Janiszewski

Overview of this book

Apache Mesos is open source cluster sharing and management software. Deploying and managing scalable applications in large-scale clustered environments can be difficult, but Apache Mesos makes it easier with efficient resource isolation and sharing across application frameworks. The goal of this book is to guide you through the practical implementation of the Mesos core along with a number of Mesos supported frameworks. You will begin by installing Mesos and then learn how to configure clusters and maintain them. You will also see how to deploy a cluster in a production environment with high availability using Zookeeper. Next, you will get to grips with using Mesos, Marathon, and Docker to build and deploy a PaaS. You will see how to schedule jobs with Chronos. We’ll demonstrate how to integrate Mesos with big data frameworks such as Spark, Hadoop, and Storm. Practical solutions backed with clear examples will also show you how to deploy elastic big data jobs. You will find out how to deploy a scalable continuous integration and delivery system on Mesos with Jenkins. Finally, you will configure and deploy a highly scalable distributed search engine with ElasticSearch. Throughout the course of this book, you will get to know tips and tricks along with best practices to follow when working with Mesos.
Table of Contents (15 chapters)
Title Page
About the Authors
About the Reviewer
Customer Feedback

Setting up the discovery service

One of the major problems with running services in a shared environment is the network. How can we make sure services can talk to each other while they could be spawned on different machines and ports? In this recipe, you will learn how to run the discovery service for Marathon to enable services to find each other and we will use the proxy approach with Traefik.

Getting ready

Before you start, ensure Marathon is up and running.

How to do it...

This solution is recommended for small and medium sized clusters with fewer than hundreds of services and fewer than thousands of instances with moderate traffic. With bigger clusters, you will probably need a different approach than a central proxy, such as consul, where you can use allegro/marathon-consul.

Before we start to think about where the proxy should be placed, remember that the more nodes you have, the more proxies you will need. On the other hand, each proxy will query Marathon so it will decrease performance...