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

Monitoring Marathon

Marathon can send logs and metrics to dedicated systems, such as Kibana for logs and Graphite for metrics. To enable them, we need to change the configuration. In this recipe, you will learn how to collect logs and metrics from Marathon.

Getting ready

Before you start, ensure Marathon is up and running. In this recipe, we will assume you have a running Graphite instance at

How to do it...

In the following example, we assume Graphite is reachable at graphite.local at port 2003 and accepts TCP packages. The following configuration instructs Marathon to send metrics every 30 seconds and to prefix them with marathon:

cat << EOF >> /etc/default/marathon

Enabling logging with logstash is similar. Let's assume logstash reads incoming logs at logstash.local at port 5000:

cat << EOF >> /etc/default/marathon