Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Towards Running Stateful Applications on Nomad
Search
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Diptanu Choudhury
August 03, 2016
1k
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Towards Running Stateful Applications on Nomad
Diptanu Choudhury
August 03, 2016
More Decks by Diptanu Choudhury
See All by Diptanu Choudhury
Chaos Engineering and design principles for building Highly Available services on the cloud
diptanu
0
490
Taming the public and private clouds with Nomad
diptanu
1
210
Distributed Scheduling with Apache Mesos in the Cloud
diptanu
1
510
Reliably shipping containers in a resource rich world using Titan
diptanu
8
2.4k
Distributed Scheduling with Apache Mesos in the Cloud
diptanu
0
410
Featured
See All Featured
DBのスキルで生き残る技術 - AI時代におけるテーブル設計の勘所
soudai
PRO
68
57k
Reality Check: Gamification 10 Years Later
codingconduct
0
2.3k
A better future with KSS
kneath
240
18k
WCS-LA-2024
lcolladotor
0
820
Paper Plane
katiecoart
PRO
2
53k
HTML-Aware ERB: The Path to Reactive Rendering @ RubyCon 2026, Rimini, Italy
marcoroth
4
550
Keith and Marios Guide to Fast Websites
keithpitt
413
23k
Writing Fast Ruby
sferik
630
63k
Typedesign – Prime Four
hannesfritz
42
3.2k
Noah Learner - AI + Me: how we built a GSC Bulk Export data pipeline
techseoconnect
PRO
0
410
Code Review Best Practice
trishagee
74
20k
How People are Using Generative and Agentic AI to Supercharge Their Products, Projects, Services and Value Streams Today
helenjbeal
1
300
Transcript
HASHICORP Towards Running Stateful Applications on Nomad Diptanu Gon Choudhury
@diptanu HashiConf US Sep 2016
Quest to increase agility and reliability Develop Build Deploy Production
Fast turnaround High Availability Control Plane for operations
Quest to increase agility and reliability Develop Build Deploy Region
1 Region 2 DC 1 DC 2 DC 3 DC 3 DC 3 DC 3
Nomad Multi DC Multi Region Diverse workload Diverse platform Built
for scale Operationally simple
Nomad Optimistic Concurrency State Coordination Service, Batch and System workloads
Application Configuration Constraints job "redis" { datacenters = ["us-east-1"] group
“cache” { count = 100 task "redis" { driver = "docker" config { image = "redis:latest" } resources { cpu = 500 memory = 256 network { mbits = 10 dynamic_ports = ["redis"] } } } }
job "redis" { datacenters = ["us-east-1"] task "redis" { driver
= "docker" config { image = "redis:latest" } resources { cpu = 500 memory = 256 network { mbits = 10 dynamic_ports = ["redis"] } } } }
Batch Scheduler Service Scheduler Restart Policies System Scheduler Consul Integration
Log Management Runtime Stats Job Plans Vault Integration TLS Sticky Volumes Disk Watchers Volume Plugins Network Plugins ACL Priorities Quotas
Nomad is a great platform for stateless workloads
Improved support and features for Stateful Applications
Nomad Jobs Task Group Task Group Task A Task B
Task C Task D Allocation Allocation Job
Allocations Allocations are instances of a task group on a
compute node Ephemeral in nature Allocations manage the life cycle of tasks within them Provides the environment and file system for the tasks
Allocation Resources CPU Shares Memory Network Ports and IPs Task
Resources Shared Resources Disk Resources
Allocation Directory Allocation directory provides a shared data directory for
tasks stdout and stderr streams of tasks are written in logs dir Each Task has a task local directory
Allocation Directory Ephemeral Disk Allocation Directory Task Dir Task Dir
Allocation Directory
Allocation Directory Allocation Directory data logs tmp local tmp Task
Dir Task Dir local tmp
Allocations Allocations are ephemeral in nature Allocations can be restarted
on a different node Allocation directory not preserved when restarted on same node They are garbage collected by Nomad after they transition to terminal state
Sticky Volumes
Sticky Volumes Prefers to restart allocation on the same nodes
to avoid replication Replicate the shared data dir and task local dirs of allocations Best effort replication, not a Distributed File Systems
group “redis” { ephemeral_disk { sticky = true size =
20000 } task “redis” { … } task “backup-agent” { … } } cache.nomad
Ephemeral Disk Shared Allocation Directory Task A Task B
Ephemeral Disk Shared Allocation Directory Task A Task B Shared
Allocation Directory Task A Task B Move
Node A Allocation Allocation Node B P2P Replication
Disk Watcher Watch dog process to monitor disk usage Allocations
get killed if they use more disk resources than they are allocated If an allocation exceeds it’s disk quota, the allocation fails permanently
The Future Data Volumes to add additional volumes to allocations
Volume plugins for materializing volumes on storage services like EBS, EFS, NFS, etc File system drivers for supporting file systems such as ZFS
Thanks! https://www.nomadproject.io/ https://github.com/hashicorp/nomad