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 now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
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
David Blomquist David Blomquist
Author Profile Icon David Blomquist
David Blomquist
Tomasz Janiszewski Tomasz Janiszewski
Author Profile Icon Tomasz Janiszewski
Tomasz Janiszewski
Marco Massenzio Marco Massenzio
Author Profile Icon Marco Massenzio
Marco Massenzio
Arrow right icon
View More author details
Toc

Table of Contents (9) Chapters Close

Preface 1. Getting Started with Apache Mesos 2. Implementing High Availability with Apache ZooKeeper FREE CHAPTER 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

Scheduling tasks


In this recipe, we will ask Mesos to run a task.

How to do it...

First of all, we need to know what task we want to schedule. To allow communication with the framework, we will prepare the HTTP API.

To handle HTTP requests, we need to implement the HTTP handler and bind it to some ports.

Let's declare the following variables in the main() function:

listen := ":9090"
webuiURL := fmt.Sprintf("http://%s%s", hostname, listen)

Let's also declare one global variable:

var taskID uint64

Tasks can be launched only when offers are available. To communicate with the offer handler, we will use a channel. If you are not familiar with Golang channels, they're similar to a message queue or pipe. Basically, you write at one end and read at another. Let's declare it globally:

var commandChan = make(chan string, 100)

Extend the FrameworkInfo definition with the just-created web UI URL:

frameworkInfo = FrameworkInfo{
        User: &user,
        Name: &name,
        Hostname: &hostname,
...
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 $19.99/month. Cancel anytime