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

State persistence


In this recipe, we will learn how to persist framework state between restarts.

How to do it...

Every time we restart our framework, it starts from scratch, losing all information about the tasks it's scheduled. After the framework goes down, Mesos kills all its tasks. This behavior is not acceptable when we want to upgrade the framework without restarting its tasks. To change this, we must do two things: tell Mesos to keep tasks after framework communication fails, and keep framework state between restarts.

In the main() function, declare the variable holding the framework failover seconds and checkpointing flag:

failoverTimeout := float64(3600)
checkpoint := true

We will use them in the framework info declaration.

Then we need to store the framework info and task state. The framework info is changed only after the subscribe method. After subscription, it's worthwhile saving, since it contains a framework that is required to reconnect.

Declare a global variable with a path to...

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