If a datastore stops

Ferry starts a stopped datastore again by itself. The volume keeps the data.

The reconciler looks at each datastore one time each 10 seconds.

1 / 4

The reconciler repairs a datastore with no action from you.

What Ferry repairs

Case	What Ferry does
The container of an `available` datastore stopped or disappeared.	Ferry starts it, or makes it again.
The creation of the datastore failed.	Ferry tries again after 1 minute. Then the delay grows, up to 30 minutes.

ferryd writes this line in its log:

Log of ferryd

datastore 'app-db' ran out of memory (limit 1 GiB) — raise the datastore's memory limit

If the datastore stops, Docker starts it again. To stop the cause, raise the memory limit.

Self-healing explains the reconciler.

Memory and CPU limits

Each datastore has a memory limit and a CPU limit. A change applies with no restart.

Back up a datastore

Ferry makes no backup of a datastore. Write the data into a file yourself, on a schedule.