@ -13,7 +13,9 @@ Command for using and attaching to LXC container (e.g. to 'worker1'): ```lxc-att
One possible limitation of the deployment process with docker swarm, is that static ip assignments [are missing in docker
swarm](https://forums.docker.com/t/docker-swarm-1-13-static-ips-for-containers/28060/13), and so the deployment process is based on the overlay networks, the inclusion of which inside the service deployment adds a degree of environmental complexity for the Galera cluster setup, especially since we use a [custom stack deployment](https://git.swarmlab.io:3000/cs171027/galera-swarm-lxc-ansible/src/branch/master/stack.yaml) for the ```mariadb-galera-swarm``` image.
For checking the service status this command is suitable with the output from below: ```docker service ls```
For checking the service status this command is suitable with the output from below:
For checking the current size of the Galera cluster - meaning all the current nodes connected to the cluster - there exist some useful commands, which should be executed inside the docker container cluster nodes (```docker exec -it {container_id} sh```), e.g inside the first MariaDB server node:
```mysql -u root -e "SHOW GLOBAL STATUS LIKE 'wsrep_cluster_size%';"```
```
mysql -u root -e "SHOW GLOBAL STATUS LIKE 'wsrep_cluster_size%';"
```
In case the result of this command is 1, it means that only one MariaDB server is running inside the cluster, which is the server from which the cluster is bootstraping from (see also inside the file ```/var/lib/mysql/grastate.dat``` if this line exists: ```safe_to_bootstrap: 1``` to confirm that this is the case).
Also, a new database, named e.g "database" and defined inside the "stack.yaml" deployment file, should initially appear inside the Galera cluster on all the MariaDB nodes: