fixes and improvements

Author: YuryHrytsuk

services/rabbit/.operations.Makefile

@@ -43,7 +43,7 @@ down: stop-cluster
 start-cluster: start-all-nodes start-loadbalancer
 
 update-cluster stop-cluster:
-	@$(error This operation may break cluster. Perform it per component)
+	@$(error This operation may break cluster. Check README for details.)
 
 #
 # Load Balancer

services/rabbit/README.md

@@ -8,9 +8,9 @@ Perform update one node at a time. Never update all nodes at the same time (this
 
 ## Graceful shutdown
 
-Normally when you shut down a RabbitMQ cluster altogether, the first node you restart should be the last one to go down, since it may have seen things happen that other nodes did not.
+Shutdown nodes one by one gracefully. Wait until the nodes is stopped and leaves the cluster. Then remove next node. When starting cluster, start nodes **in the reverse order**! For example, if you shutdown node01, then node02 and lastly node03, first start node03 then node02 and finally node03.
 
-If all Nodes were shutdown simultaneously, use force_boot (https://www.rabbitmq.com/docs/man/rabbitmqctl.8#force_boot)
+If all Nodes were shutdown simultaneously, then you will see mnesia tables errors in node's logs. Restarting node solves the issue . Documentation also mentions force_boot CLI command in this case (see https://www.rabbitmq.com/docs/man/rabbitmqctl.8#force_boot)
 
 #### Community discussions
 mnesia errors after all rabbit nodes (docker services) restart:

services/rabbit/docker-compose.node0x.yml.j2

@@ -72,9 +72,6 @@ configs:
   rabbitmq.conf:
     # no rolling update since it requires full cluster restart
     file: ./configs/rabbitmq.conf
-  haproxy.cfg:
-    file: ./configs/haproxy.cfg
-    name: rabbit_haproxy_conf_{{ "./configs/haproxy.cfg" | sha256file | substring(0,10) }}
 
 secrets:
   rabbit_erlang_cookie: