Getting Started with Apache Mesos
summary
Mesos treats many servers as one and advertises per-host CPU, memory, disk and ports to frameworks like Marathon, Chronos, Spark and a Jenkins plugin; Mesos masters use ZooKeeper for HA and odd numbers (3,5,7) are typical. The scheduler uses CRF (dominant resource fairness) so CPU‑heavy and memory‑heavy frameworks share fairly. Marathon enforces desired instance counts and restarts unhealthy tasks; Chronos runs cluster cron jobs. Languages: C++, Java, Scala, Python, Go, Ruby. Memory overuse triggers the Linux OOM killer.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:32Language Bindings
- 7:57Spark
- 13:44Clusters
- 15:14Monitoring and Metrics Collection
- 15:52Persistent Storage
- 20:02Requirements
- 22:24Deploying Applications
- 23:08Health Checks
related talks
57mA Distributed and Fault-Tolerant Application with Apache Mesos & Apache Aurora
39mHow we learned to love the Data Center Operating System
41mEfficient cluster resource management by using Cook and Mesos
41mEfficient cluster resource management by using Cook and Mesos
46mContainer Pods with Docker Compose in Apache Mesos
27mDowntime is not an option
35mHow to Train Jenkins?
28mDesigning for Failure: How to Manage Thousands of Hosts Through Automation