ConceptsSelf-healing
When ferryd starts again
At its start, ferryd marks the interrupted work, installs the routes and repairs the rest.
Mark. Ferry marks the interrupted deploys and job runs as failed.
1 / 4
Your apps get traffic again immediately, because each route is there before the proxy accepts connections.
Deploy again
Ferry does not try an interrupted deploy again. Start it again.
ferry deploy NAMEThe four steps
| Step | What Ferry does |
|---|---|
| Mark | Deploys that were queued, building or deploying become build_failed or deploy_failed. The error is "interrupted by server restart". Job runs in progress become failed. |
| Routes | Ferry installs the routes of each service before the proxy accepts connections. |
| Repair | Ferry removes the containers of interrupted deploys, starts the instances that are not there and restarts datastores. |
| Loops | Ferry starts the reconciler loop, the route watcher, the out-of-memory watcher and the cron scheduler. It continues the creation of datastores that was in progress. |
See also If the server stops during a deploy.