Prerequisites
...
Other services like Mixer, Rest Server, and Archival process high availability is achieved with Docker Swarm.
A swarm consists of multiple Docker hosts which run in swarm mode and act as managers (to manage membership and delegation) and workers (which run swarm services). A given Docker host can be a manager, a worker, or perform both roles. When you create a service, you define its optimal state (number of replicas, network and storage resources available to it, ports the service exposes to the outside world, and more). Docker works to maintain that desired state. For instance, if a worker node becomes unavailable, Docker schedules that node’s tasks on other nodes. A task is a running container which is part of a swarm service and managed by a swarm manager, as opposed to a standalone container.
To learn more about Docker Swarm Mode, see Docker Swarm Concepts
...
However, if the Docker engine becomes down, it is restarted by the Linux OS automatically in most of the cases. If in case, it does not restart, manual intervention would be required to start it. FOr the time it is down, the active containers continue to run. However, all the container orchestration features are not available; i.e. no new node can be added/removed to/from the cluster during the time the Docker engine is down.
Limitations of Redundant Deployment
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|