Note: Assumes Docker Compose 2 is available.
Unless otherwise stated all commands should be run from the <project root>/docker directory.
This will start a three-node cluster, with 2 admin containers. The cluster nodes will run an election, selecting one of the nodes as the leader.
Containers will be named as follows:
| Container | Description |
|---|---|
| aeron-engine0-1 | Cluster Node |
| aeron-engine1-1 | Cluster Node |
| aeron-engine2-1 | Cluster Node |
| aeron-admin1-1 | Admin Node |
| aeron-admin2-1 | Admin Node |
- First, build the source code by running
./gradlewin the project root directory - Then, build the containers with
docker compose build --no-cache
Start the cluster and admin containers by running docker compose up -d
To find the leader (e.g. to stop it to test failover), you can either review the logs of the containers with docker compose logs and search for LEADER (
e.g. docker compose logs | grep LEADER), or use the script ./docker_find_leader.sh.
Both admin containers can be used at the same time. Change aeron-admin1-1 for aeron-admin2-1 as needed.
(assumes a container named aeron-admin1-1 is running)
docker exec -it aeron-admin1-1 java -jar admin-uber.jar
Within the admin, you can then connect to the cluster:
connectTo stop a specific container, run:
docker compose stop <container name> where <container name> matches the name of the container you want to stop.
To stop all the containers, and remove any networking changes, run:
docker compose down
The cluster containers contain a number of Aeron operations tools. These are available via scripts such as aeronstat-single.sh and snapshot.sh.