Process Migration in the Orchestration World
summary
Demonstrates live container checkpoint and restart on an Apache Mesos mini‑cluster using runc and DMTCP, checkpointing a Redis instance and preserving an in‑memory key across failure and restore; checkpoint file is ~2.9 MB in the demo and periodic checkpointing is set to 5s. Notes that migration cost scales with memory (1 GB → ~10 s at 100 MB/s) and that Mesos currently lacks integrated task states for checkpoint/restore so integration work remains.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:38Overview
- 1:12Stateless vs. Stateful Applications
- 2:28Scheduling Stateless vs. Statelul Applications
- 4:27How to Improve Scheduling of Stateful Applications?
- 5:28Terminology
- 6:16How to Migrate a Process/Container/VM?
- 8:41What is Checkpointing?
- 11:30Checkpointing Use Cases
- 14:07Stateful Applications with Checkpointing
- 17:03The datacenter abstraction
- 17:48Resource offers
- 22:16Mesos mechanics are fair
- 34:18Future Work: Checkpointing as a Service
related talks
52mNightmares of a Container Orchestration System
35mFault Tolerant Frameworks - Making Use of CNI Without Docker
15mKeynote: State of the Mesos
31mScaling a Distributed Container Management System: Diego Performance
42mStreaming Data Pipelines on Apache Mesos: Lessons Learned
17mMeces: Latency-efficient Rescaling via Prioritized State Migration for Stateful...
18mIn-Memory Key-Value Store Live Migration with NetMigrate
41mEfficient cluster resource management by using Cook and Mesos
