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

Acknowledging task updates

In this recipe, we will learn how Mesos communicates the task's state changes and how to handle these changes.

How to do it...

Right now, we should be able to spawn new tasks on a Mesos cluster but when we deploy tasks with an invalid command, such as false:

curl -X POST "http://localhost:9090/?cmd=false"

This task immediately ends with an exit code equal to 1. In the Mesos UI, we can see these tasks have failed but it's not presented in completed tasks. This is because each task state update needs to be acknowledged by the framework.

In the subscribe event switch, add the following case:

case Event_UPDATE:
     log.Printf("Handle update returns: %v", handleUpdate(event.Update))

Then implement the handleUpdate function:

func handleUpdate(update *Event_Update) error {
      return call(&Call{
             Type: Call_ACKNOWLEDGE.Enum(),
             Acknowledge: &Call_Acknowledge{
                   AgentId: update.Status.AgentId,
                   TaskId: update...