Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Apache Mesos Cookbook

You're reading from   Apache Mesos Cookbook Efficiently handle and manage tasks in a distributed environment

Arrow left icon
Product type Paperback
Published in Aug 2017
Publisher Packt
ISBN-13 9781785884627
Length 146 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (3):
Arrow left icon
Marco Massenzio Marco Massenzio
Author Profile Icon Marco Massenzio
Marco Massenzio
 Blomquist Blomquist
Author Profile Icon Blomquist
Blomquist
Tomasz Janiszewski Tomasz Janiszewski
Author Profile Icon Tomasz Janiszewski
Tomasz Janiszewski
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
1. Getting Started with Apache Mesos FREE CHAPTER 2. Implementing High Availability with Apache ZooKeeper 3. Running and Maintaining Mesos 4. Understanding the Scheduler API 5. Managing Containers 6. Deploying PaaS with Marathon 7. Job Scheduling with Metronome 8. Continuous Integration with Jenkins

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...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images