Updated: February 16, 2017

DC/OS applications lose their state when they terminate and are relaunched. In some contexts, for instance, if your application uses MySQL, or if you are using a stateful service like Kafka or Cassandra, you’ll want your application to preserve its state. Use local persistent volumes or external volumes to enable tasks to be restarted without data loss. Learn how to configure your cluster to use persistent volumes.

External Persistent Volumes

Use external volumes when fault-tolerance is crucial for your app. If a host fails, the native Marathon instance reschedules your app on another host, along with its associated dat...

Local Persistent Volumes

When you specify a local volume or volumes, tasks and their associated data are “pinned” to the node they are first launched on and will be relaunched on that node if t...