Apache Mesos Overview and Integration

Apache Mesos Overview and
Integration:
Docker, Kubernetes, and Beyond
Alex Barreto
Disney Interactive - Data Technology
alex.barreto@disney.com
@shakamunyi

What you should take away
● Overview
● History
● Use Cases
● Integration
– Dokah, dokah, dokah
– Kubernetes

What is Apache Mesos?
Apache Mesos is a cluster manager that
provides efficient resource isolation and sharing
across distributed applications, or frameworks.
It can run Hadoop, MPI, Hypertable, Spark,
Elastic Search, Storm, Aurora, Marathon ... and
other applications on a dynamically shared pool of
nodes.

Rephrased:
- Mesos is a distributed systems kernel -
● Mesos is built using the same principles as the Linux
kernel, only at a different level of abstraction. The
Mesos kernel runs on every machine and provides
applications (e.g., Hadoop, Spark, Kafka, Elastic
Search) with API’s for resource management and
scheduling across entire datacenter and cloud
environments.
● Or you could think of it as a distributed system to build
distributed systems.

Project Highlights
● Top-level Apache project ~ 1 year (mesos.apache.org)
● Scales to 10,000s of nodes
● Obviates the need for virtual machines in some use cases
● Isolation for CPU, RAM, I/O, FS, etc.
● Fault-tolerant leader election (HA) based on Zookeeper
● API's in C++, Java/Scala, Python, Go, Erlang, Haskell.
● Web UI for inspecting state
● Available for Linux, OpenSolaris, Mac OSX

Who is using Mesos? - This list is old.

Apache Mesos Overview and Integration

Google Refs
● The Datacenter as a Computer: An Introduction to the Design
of Warehouse-Scale Machines
http://research.google.com/pubs/pub35290.html
● 2011 GAFS Omega John Wilkes:
http://youtu.be/0ZFMlO98Jkc
● Omega: flexible, scalable schedulers for large compute
clusters
http://eurosys2013.tudos.org/wp-content/uploads/2013/paper
/Schwarzkopf.pdf
● Taming Latency Variability and Scaling Deep Learning
https://plus.google.com/u/0/+ResearchatGoogle/posts/C1dPh
QhcDRv
History

Understanding of Datacenter Computing
Google has been doing data center computing for
years to address the complexities of large-scale
data workflows:
● Leveraging the modern kernel isolation. (cgroups)
● Containerization !Virtualization (lmctfy - Docker)
● Most (>80) jobs are batch jobs, but the majority of
resources(55-80%) are allocated to service jobs.
● Mixed workloads, multi-tenancy
● Relatively high utilization rates
● JVM? Not so much...
● Reality: scheduling batch is simple;
– scheduling services is hard/expensive.

Refs.
● The Datacenter as a Computer: An Introduction
to the Design of Warehouse-Scale Machines
– http://research.google.com/pubs/pub35290.html
● GAFS Omega John Wilkes
– https://www.youtube.com/watch?v=0ZFMlO98Jkc
● Taming Latency Variability and Scaling Deep
Learning
– http://youtu.be/nK6daeTZGA8

Why Mesos?
● Many existing solutions had architectural
deficiencies around a constraining model.
– Everything is a “job”, good for batch.
– Everything was a “service”, good for PaaS.
– What happens when you want to write your own
distributed application? (no primitives)
– What happens when you want to write your own
scheduler (elastic service). Reinvent the Square
wheel.

The New Reality
● New applications need to be:
– Fault Tolerant (Withstand failure)
– Scalable (Not crumble under it's own weight)
– Elastic (Can grow and shrink based on demand)
– Multi-tenent (It can't have it's own dedicated cluster)
● Must play nice with the other kids.
● So what does that really mean?

Distributed Applications
● “There's Just No Getting Around It: You're Building a Distributed System” Mark Cavage
– queue.acm.org/detail.cfm?id=2482856
● Key takeaways on architecture:
– Decompose the business applications into discrete services on the boundaries of fault
domains, scaling, and data workload.
– Make as many things as possible stateless
– When dealing with state, deeply understand CAP, latency, throughput, and durability
requirements.
“Without practical experience working on successful—and failed—systems, most engineers take
a "hopefully it works" approach and attempt to string together off-the-shelf software, whether
open source or commercial, and often are unsuccessful at building a resilient, performant system.
In reality, building a distributed system requires a methodical approach to requirements along the
boundaries of failure domains, latency, throughput, durability, consistency, and desired SLAs for
the business application at all aspects of the application.”

Google Refs
clusters
/Schwarzkopf.pdf
QhcDRv
Emerging
at Berkeley

Prior Practice: Dedicated Servers
• low utilization rates
• longer time to ramp up new services
DATACENTER

Prior Practice: Virtualization
DATACENTER PROVISIONED VMS
• even more machines to manage
• substantial performance decrease
due to virtualization
• VM licensing costs

Prior Practice: Static Partitioning
STATIC PARTITIONING
• even more machines to manage
• substantial performance decrease
due to virtualization
• VM licensing costs
• failures make static partitioning
more complex to manage
DATACENTER

What are the costs of Single Tenancy?
0%
25%
50%
75%
100%
RAILS CPU
LOAD
MEMCACHED
CPU LOAD
0%
25%
50%
75%
100%
HADOOP CPU
LOAD
0%
25%
50%
75%
100%
tt
0%
25%
50%
75%
100%
Rails
Memcached
Hadoop
COMBINED CPU LOAD (RAILS,
MEMCACHED, HADOOP)

MESOS
Mesos: One Large Pool of Resources
“We wanted people to be able to program
for the datacenter just like they program
for their laptop."
Ben Hindman
DATACENTER

Kernel
Apps
servicesbatch
Frameworks
Python
JVM
C
++
Workloads
distributed file system
Chronos
DFS
distributed resources: CPU, RAM, I/O, FS, rack locality, etc. Cluster
Storm
Kafka JBoss Django RailsImpalaScalding
Marathon
SparkHadoopMPI
MySQL
Mesos – architecture

Google Refs
clusters
/Schwarzkopf.pdf
QhcDRv
Use Cases

Case Study: Twitter (bare metal / on premise)
“Mesos is the cornerstone of our elastic compute infrastructure –
it’s how we build all our new services and is critical for Twitter’s
continued success at scale. It's one of the primary keys to our
data center efficiency."
Chris Fry, SVP Engineering
blog.twitter.com/2013/mesos-graduates-from-apache-incubation
wired.com/gadgetlab/2013/11/qa-with-chris-fry/
• key services run in production: analytics, typeahead, ads
• Twitter engineers rely on Mesos to build all new services
• instead of thinking about static machines, engineers think
about resources like CPU, memory and disk
• allows services to scale and leverage a shared pool of
servers across datacenters efficiently
• reduces the time between prototyping and launching

Case Study: Airbnb (fungible cloud infrastructure)
“We think we might be pushing data science in the field of travel
more so than anyone has ever done before… a smaller number
of engineers can have higher impact through automation on
Mesos."
Mike Curtis, VP Engineering
gigaom.com/2013/07/29/airbnb-is-engineering-itself-into-a-data...
• improves resource management and efficiency
• helps advance engineering strategy of building small teams
that can move fast
• key to letting engineers make the most of AWS-based
infrastructure beyond just Hadoop
• allowed company to migrate off Elastic MapReduce
• enables use of Hadoop along with Chronos, Spark, Storm, etc.

Case Study: HubSpot (cluster management)
Tom Petr
youtu.be/ROn14csiikw
• 500 deployable objects; 100 deploys/day to
production; 90 engineers; 3 devops on Mesos
cluster
• “Our QA cluster is now a fixed $10K/month —
that used to fluctuate”

Dock-ah, dock-ah, dock-ah
"If a Docker application is a Lego brick, Kubernetes would be like a kit
for building the Millennium Falcon and the Mesos cluster would be like
a whole Star Wars universe made of Legos." ~ Solomon
● Mesos used to have plugable add-ons for docker, and now they are 1st
classed into the core.
– Lots of churn between 0.20-0.21 on feedback from the field.
● It enables programmatic scheduling of containers from batch (cronos), to
service orchestration (marathon & Aurora).
● Common deployment is Marathon + HA-Proxy + Docker running from
O(10^1) - O(10^3) with mesos clusters O(10^4).
● Some users are exploring customized elastic batch.
● Custom frameworks are quite a large space, we only see a tip of the iceburg.

Kubernetes+Mesos = Awesome
● Kubernetes provides robust declarative
primitives for distributed micro-services.
● Mesos provides an imperative framework by
which application developers can define
scheduling policy in a programmatic fashion.
● When leveraged together it provides a data-
center with the ability to both.
– Both batch and service.

Kubernetes+Mesos cont.
● Launching pods
– Implement Kube-scheduler API
– Pick a Pod (FCFS), match it to an offer.
– Launch it!
– Kubelet as Executor+Containerizer
● Pod Labels: for Service Discovery + Load Balancing
● Running multi-node on GCE
● Replication Control
● Use resource shapes to schedule pods
● Even smarter scheduling

Coming – “Soon-ish”
● Primitives to support Stateful Services (HDFS,
Cassandra, etc.)
– Persistent disk data.
– Lazy resource reservation
– Expanded Disk Isolation
● I/O
● FS/Mount namespace
● Support multiple spindles
– Dynamic slave attributes.

“Soon-ish” - part 2
● Opportunistic Offers
– Free-for-all like Omega.
– Requires Framework API modifications
– Increased utilization at cloud-scale.

Google Refs
clusters
/Schwarzkopf.pdf
QhcDRv
Thank You!
mesos.apache.org
@shakamunyi

Apache Mesos Overview and Integration

Recommended

More Related Content

What's hot (20)

Similar to Apache Mesos Overview and Integration (20)

Recently uploaded (20)

Apache Mesos Overview and Integration