### 歡迎訪問我的GitHub
> 這裡分類和彙總了欣宸的全部原創(含配套原始碼)：[https://github.com/zq2599/blog_demos](https://github.com/zq2599/blog_demos)

- 本章是《Docker下RabbitMQ四部曲》系列的終篇，今天的我們一起來體驗Rabbit'MQ叢集的高可用能力，看看RabbitMQ叢集中的部分節點當機時，是否還能生產和消費訊息；
### 前文連結
- 《Docker下RabbitMQ四部曲》的前三篇連結如下：
1. [《Docker下RabbitMQ四部曲之一：極速體驗(單機和叢集)》](http://blog.itpub.net/70017844/viewspace-2897069/)；
2. [《Docker下RabbitMQ四部曲之二：細說RabbitMQ映象製作》](http://blog.itpub.net/70017844/viewspace-2897380/)；
3. [《Docker下RabbitMQ四部曲之三：細說java開發》](http://blog.itpub.net/70017844/viewspace-2897675/)；

### 實戰概要
- 今天實戰的步驟如下：
1. 製作docker-compose.yml檔案，為每個容器配置好引數；
2. 啟動所有容器，包括RabbitMQ叢集、訊息生產者的web應用、訊息消費者的web應用；
3. 逐個停止叢集中的RabbitMQ容器，每停止一個，就驗證一次訊息的生產和消費；
4. 逐個恢復叢集中的RabbitMQ容器，每恢復一個，就驗證一次訊息的生產和消費；

### 製作docker-compose.yml檔案

- 本次實戰會建立6個容器，整理如下：

| 容器名                | IP地址     | 作用                     |
| --------------------- | ---------- | ------------------------ |
| hacluster_rabbit1_1   | 172.19.0.2 | RabbitMQ主節點           |
| hacluster_rabbit2_1   | 172.19.0.3 | RabbitMQ從節點，記憶體節點 |
| hacluster_rabbit3_1   | 172.19.0.4 | RabbitMQ從節點           |
| hacluster_producer_1  | 172.19.0.5 | web應用，負責生產訊息    |
| hacluster_consumer1_1 | 172.19.0.6 | web應用，負責消費訊息    |
| hacluster_consumer2_1 | 172.19.0.7 | web應用，負責消費訊息    |

- 前面章節的實戰中，我們也建立了上述六個容器，今天依然是六個，並且身份角色不變，變化的地方主要是以下三點：
1. 負責生產訊息的hacluster_producer_1容器，前面章節只連線了一個RabbitMQ容器，本章會連線三個；
2. 負責消費訊息的hacluster_consumer1_1，前面章節只連線了一個RabbitMQ容器，本章會連線三個；
3. 負責消費訊息的hacluster_consumer2_1，前面章節只連線了一個RabbitMQ容器，本章會連線三個；

- 基於以上總結，我們寫出的docker-compose.yml檔案內容如下：
```yml
version: '2'
services:
  rabbit1:
    image: bolingcavalry/rabbitmq-server:0.0.3
    hostname: rabbit1
    ports:
      - "15672:15672"
    environment:
      - RABBITMQ_DEFAULT_USER=admin
      - RABBITMQ_DEFAULT_PASS=888888
  rabbit2:
    image: bolingcavalry/rabbitmq-server:0.0.3
    hostname: rabbit2
    depends_on:
      - rabbit1
    links:
      - rabbit1
    environment:
     - CLUSTERED=true
     - CLUSTER_WITH=rabbit1
     - RAM_NODE=true
     - HA_ENABLE=true
    ports:
      - "15673:15672"
  rabbit3:
    image: bolingcavalry/rabbitmq-server:0.0.3
    hostname: rabbit3
    depends_on:
      - rabbit2
    links:
      - rabbit1
      - rabbit2
    environment:
      - CLUSTERED=true
      - CLUSTER_WITH=rabbit1
    ports:
      - "15675:15672"
  producer:
    image: bolingcavalry/rabbitmqproducer:0.0.2-SNAPSHOT
    hostname: producer
    depends_on:
      - rabbit3
    links:
      - rabbit1:rabbitmqhost1
      - rabbit2:rabbitmqhost2
      - rabbit3:rabbitmqhost3
    ports:
      - "18080:8080"
    environment:
      - mq.rabbit.address=rabbitmqhost1:5672,rabbitmqhost2:5672,rabbitmqhost3:5672
      - mq.rabbit.username=admin
      - mq.rabbit.password=888888
  consumer1:
    image: bolingcavalry/rabbitmqconsumer:0.0.5-SNAPSHOT
    hostname: consumer1
    depends_on:
      - producer
    links:
      - rabbit1:rabbitmqhost1
      - rabbit2:rabbitmqhost2
      - rabbit3:rabbitmqhost3
    environment:
     - mq.rabbit.address=rabbitmqhost1:5672,rabbitmqhost2:5672,rabbitmqhost3:5672
     - mq.rabbit.username=admin
     - mq.rabbit.password=888888
     - mq.rabbit.queue.name=consumer1.queue
  consumer2:
    image: bolingcavalry/rabbitmqconsumer:0.0.5-SNAPSHOT
    hostname: consumer2
    depends_on:
      - consumer1
    links:
      - rabbit1:rabbitmqhost1
      - rabbit2:rabbitmqhost2
      - rabbit3:rabbitmqhost3
    environment:
      - mq.rabbit.address=rabbitmqhost1:5672,rabbitmqhost2:5672,rabbitmqhost3:5672
      - mq.rabbit.username=admin
      - mq.rabbit.password=888888
      - mq.rabbit.queue.name=consumer2.queue
```

**以上的docker-compose.yml檔案，有以下兩點需要注意：**
- rabbit2：增加了一個環境變數**HA_ENABLE=true**，[《Docker下RabbitMQ四部曲之二：細說RabbitMQ映象製作》](http://blog.itpub.net/70017844/viewspace-2897380/)一文中分析映象製作的時候曾提到過，容器建立時startrabbit.sh指令碼中會檢查這個環境變數，如果為true，就會執行命令：**rabbitmqctl set_policy HA '^(?!amq\.).*' '{"ha-mode": "all"}'**，該命令會將佇列設定為映象模式，在三個Rabbit MQ之間同步；
- producer、consumer1、consumer3這三個容器的環境變數**mq.rabbit.address**，都設定成了三個RabbitMQ容器的地址加埠：**rabbitmqhost1:5672,rabbitmqhost2:5672,rabbitmqhost3:5672**；

### 啟動所有容器
- 在剛剛建立的docker-compose.yml檔案所在目錄下執行命令**docker-compose up -d**，即可建立所有容器，建立完成後執行以下操作來確認是否啟動成功：
- 例如我的電腦IP地址是**192.168.119.155**，那麼在瀏覽器輸入地址：192.168.119.155:15672即可訪問RabbitMQ的管理頁面，使用者名稱：admin，密碼：888888，如下圖：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083738831.png)
- 點選"Exchanges"這個Tab頁，如下圖，看到交換機建立成功，HA模式：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083738890.png)
- 點選"Queues"這個Tab頁，如下圖，看到兩個佇列建立成功，HA模式：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083738980.png)
- 在瀏覽器輸入：http://192.168.119.155:18080/send/aaa/bbb ，即可控制容器hacluster_producer_1 生產一條訊息，如下圖：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083739191.png)
- 在控制檯輸入**docker logs -f hacluster_consumer1_1**，即可看到hacluster_consumer1_1 消費訊息的日誌，如下：
```shell
2018-05-19 11:21:44.217  INFO 1 --- [           main] c.b.r.RabbitmqconsumerApplication        : Started RabbitmqconsumerApplication in 29.099 seconds (JVM running for 39.398)
2018-05-19 11:36:21.332  INFO 1 --- [cTaskExecutor-1] c.b.r.receiver.FanoutReceiver            : receive message : hello, aaa, bbb, 2018-05-19 11:36:21
```
- 看來整個RabbitMQ叢集的生產和消費是沒有問題的，接下來透過停止容器的方式來模擬生產環境的當機；

### 逐個停止叢集中的RabbitMQ容器
- 先停hacluster_rabbit1_1 ，執行命令**docker stop hacluster_rabbit1_1**，如下：
```shell
root@maven:~# docker stop hacluster_rabbit1_1
hacluster_rabbit1_1
```
- 去管理頁面看看，由於hacluster_rabbit1_1容器已經停止了，所以我們要訪問hacluster_rabbit2_1容器提供的web頁面：http://192.168.119.155:15673，如下圖紅框，可以看見頁面提示節點故障：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083739305.png)
- 交換機和佇列的頁面並無異常；
- 在瀏覽器輸入：http://192.168.119.155:18080/send/aaa/bbb ，嘗試傳送一條訊息，響應時間明顯變長，但是依然會返回操作成功；
- 在控制檯輸入**docker logs -f hacluster_producer_1**，檢視生產訊息的web容器的日誌，如下：
```shell
2018-05-19 11:43:22.681  WARN 1 --- [172.19.0.2:5672] c.r.c.impl.ForgivingExceptionHandler     : An unexpected connection driver error occured (Exception message: Connection reset)
2018-05-19 11:43:22.703 ERROR 1 --- [172.19.0.2:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 11:53:31.836  INFO 1 --- [io-8080-exec-10] o.s.a.r.c.CachingConnectionFactory       : Attempting to connect to: [rabbitmqhost1:5672, rabbitmqhost2:5672, rabbitmqhost3:5672]
2018-05-19 11:53:46.878  INFO 1 --- [io-8080-exec-10] o.s.a.r.c.CachingConnectionFactory       : Created new connection: connectionFactory#4ae3c1cd:1/SimpleConnection@44028da7 [delegate=amqp://admin@172.19.0.3:5672/, localPort= 37818]
```
- 從日誌中可以清晰的看到，停止hacluster_rabbit1_1容器是，訊息生產者會立即報異常，但是不會自動重連，等到傳送訊息的時候，才會連線到新的RabbitMQ，這次連線的是hacluster_rabbit2_1 ；
- 在控制檯輸入**docker logs -f hacluster_consumer1_1**，檢視消費訊息的web容器的日誌，如下：
```shell
2018-05-19 11:38:14.945  INFO 1 --- [cTaskExecutor-1] c.b.r.receiver.FanoutReceiver            : receive message : hello, aaa, bbb, 2018-05-19 11:38:14
2018-05-19 11:43:22.672  WARN 1 --- [172.19.0.2:5672] c.r.c.impl.ForgivingExceptionHandler     : An unexpected connection driver error occured (Exception message: Connection reset)
2018-05-19 11:43:22.726 ERROR 1 --- [172.19.0.2:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 11:43:23.163  INFO 1 --- [cTaskExecutor-1] o.s.a.r.l.SimpleMessageListenerContainer : Restarting Consumer@9f116cc: tags=[{amq.ctag-0csUBn5OQiTGEphcGI2p3A=consumer1.queue}], channel=Cached Rabbit Channel: PublisherCallbackChannelImpl: AMQChannel(amqp://admin@172.19.0.2:5672/,1), conn: Proxy@42dd311 Shared Rabbit Connection: SimpleConnection@5a1a52da [delegate=amqp://admin@172.19.0.2:5672/, localPort= 34240], acknowledgeMode=AUTO local queue size=0
2018-05-19 11:43:23.181  INFO 1 --- [cTaskExecutor-2] o.s.a.r.c.CachingConnectionFactory       : Attempting to connect to: [rabbitmqhost1:5672, rabbitmqhost2:5672, rabbitmqhost3:5672]
2018-05-19 11:43:29.042  INFO 1 --- [cTaskExecutor-2] o.s.a.r.c.CachingConnectionFactory       : Created new connection: connectionFactory#45f45fa1:1/SimpleConnection@2b9e231d [delegate=amqp://admin@172.19.0.3:5672/, localPort= 49624]
2018-05-19 11:53:46.899  INFO 1 --- [cTaskExecutor-2] c.b.r.receiver.FanoutReceiver            : receive message : hello, aaa, bbb, 2018-05-19 11:53:31
```
- 從日誌上可以看出：**RabbitMQ當機的時候，消費者會立即重連到叢集中的其他機器；**(日誌關鍵字：Created new connection)
- 停掉RabbitMQ叢集中的第二個容器，執行命令**docker stop hacluster_rabbit2_1**；
- 訪問管理頁面的時候，要輸入容器hacluster_rabbit3_1的地址：http://192.168.119.155:15675，基本情況如下圖，兩個節點的問題都能看到：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083739420.png)
- 在瀏覽器輸入：http://192.168.119.155:18080/send/aaa/bbb ，嘗試傳送一條訊息，響應時間再次明顯變長，但是依然會返回操作成功；
- 在控制檯輸入**docker logs -f hacluster_producer_1**，檢視生產訊息的web容器的日誌，如下，提示重連成功，這次連線到了容器hacluster_rabbit3_1 ：
```shell
2018-05-19 12:07:45.322  WARN 1 --- [172.19.0.3:5672] c.r.c.impl.ForgivingExceptionHandler     : An unexpected connection driver error occured (Exception message: Connection reset)
2018-05-19 12:07:45.334 ERROR 1 --- [172.19.0.3:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 12:07:45.336 ERROR 1 --- [172.19.0.3:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 12:12:06.404  INFO 1 --- [nio-8080-exec-4] o.s.a.r.c.CachingConnectionFactory       : Attempting to connect to: [rabbitmqhost1:5672, rabbitmqhost2:5672, rabbitmqhost3:5672]
2018-05-19 12:12:41.467  INFO 1 --- [nio-8080-exec-4] o.s.a.r.c.CachingConnectionFactory       : Created new connection: connectionFactory#4ae3c1cd:2/SimpleConnection@6d23e50 [delegate=amqp://admin@172.19.0.4:5672/, localPort= 54310]
```
- 在控制檯輸入**docker logs -f hacluster_consumer1_1**，檢視消費訊息的web容器的日誌，如下：
```shell
2018-05-19 12:07:45.327  WARN 1 --- [172.19.0.3:5672] c.r.c.impl.ForgivingExceptionHandler     : An unexpected connection driver error occured (Exception message: Connection reset)
2018-05-19 12:07:45.346 ERROR 1 --- [172.19.0.3:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 12:07:45.348 ERROR 1 --- [172.19.0.3:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 12:07:45.427  INFO 1 --- [cTaskExecutor-2] o.s.a.r.l.SimpleMessageListenerContainer : Restarting Consumer@317c5a8a: tags=[{amq.ctag-ZKT8Q4gcU9v7bA-lNOUEFQ=consumer1.queue}], channel=Cached Rabbit Channel: PublisherCallbackChannelImpl: AMQChannel(amqp://admin@172.19.0.3:5672/,1), conn: Proxy@42dd311 Shared Rabbit Connection: SimpleConnection@2b9e231d [delegate=amqp://admin@172.19.0.3:5672/, localPort= 49624], acknowledgeMode=AUTO local queue size=0
2018-05-19 12:07:45.432  INFO 1 --- [cTaskExecutor-3] o.s.a.r.c.CachingConnectionFactory       : Attempting to connect to: [rabbitmqhost1:5672, rabbitmqhost2:5672, rabbitmqhost3:5672]
2018-05-19 12:08:07.352  INFO 1 --- [cTaskExecutor-3] o.s.a.r.c.CachingConnectionFactory       : Created new connection: connectionFactory#45f45fa1:2/SimpleConnection@71dadbb0 [delegate=amqp://admin@172.19.0.4:5672/, localPort= 34416]
2018-05-19 12:12:56.869  INFO 1 --- [cTaskExecutor-3] c.b.r.receiver.FanoutReceiver            : receive message : hello, aaa, bbb, 2018-05-19 12:12:06
```
日誌顯示，也是連到了容器hacluster_rabbit3_1 ，並且消費訊息成功；
- 停掉RabbitMQ叢集中的第三個容器（也是最後一個），執行命令**docker stop hacluster_rabbit3_1**；
- 這次沒有管理頁面看了......
- 在瀏覽器輸入：http://192.168.119.155:18080/send/aaa/bbb ，嘗試傳送一條訊息，長時間等待後，頁面提示錯誤如下圖：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083739523.png)
- 檢視容器hacluster_producer_1的日誌，如下：
```shell
2018-05-19 12:18:27.812  WARN 1 --- [172.19.0.4:5672] c.r.c.impl.ForgivingExceptionHandler     : An unexpected connection driver error occured (Exception message: Connection reset)
2018-05-19 12:18:27.813 ERROR 1 --- [172.19.0.4:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 12:18:27.813 ERROR 1 --- [172.19.0.4:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 12:18:55.836  INFO 1 --- [nio-8080-exec-7] o.s.a.r.c.CachingConnectionFactory       : Attempting to connect to: [rabbitmqhost1:5672, rabbitmqhost2:5672, rabbitmqhost3:5672]
2018-05-19 12:19:50.921 ERROR 1 --- [nio-8080-exec-7] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.amqp.AmqpIOException: java.net.UnknownHostException: rabbitmqhost3] with root cause

java.net.UnknownHostException: rabbitmqhost3
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184) ~[na:1.8.0_111]
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_111]
        at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_111]
        at com.rabbitmq.client.impl.SocketFrameHandlerFactory.create(SocketFrameHandlerFactory.java:60) ~[amqp-client-5.1.2.jar!/:5.1.2]
        at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:955) ~[amqp-client-5.1.2.jar!/:5.1.2]
        at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:907) ~[amqp-client-5.1.2.jar!/:5.1.2]
        at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:847) ~[amqp-client-5.1.2.jar!/:5.1.2]
        at org.springframework.amqp.rabbit.connection.AbstractConnectionFactory.createBareConnection(AbstractConnectionFactory.java:449) ~[spring-rabbit-2.0.3.RELEASE.jar!/:2.0.3.RELEASE]
        at org.springframework.amqp.rabbit.connection.CachingConnectionFactory.createConnection(CachingConnectionFactory.java:614) ~[spring-rabbit-2.0.3.RELEASE.jar!/:2.0.3.RELEASE]
        at org.springframework.amqp.rabbit.connection.CachingConnectionFactory.createBareChannel(CachingConnectionFactory.java:564) ~[spring-rabbit-2.0.3.RELEASE.jar!/:2.0.3.RELEASE]
        at org.springframework.amqp.rabbit.connection.CachingConnectionFactory.getCachedChannelProxy(CachingConnectionFactory.java:538) ~[spring-rabbit-2.0.3.RELEASE.jar!/:2.0.3.RELEASE]
        at org.springframework.amqp.rabbit.connection.CachingConnectionFactory.getChannel(CachingConnectionFactory.java:520) ~[spring-rabbit-2.0.3.RELEASE.jar!/:2.0.3.RELEASE]
......
...
```
- 如上所示，異常資訊為連線RabbitMQ伺服器失敗；
- 檢視容器hacluster_consumer1_1的日誌，如下：
```shell
2018-05-19 12:18:27.815  WARN 1 --- [172.19.0.4:5672] c.r.c.impl.ForgivingExceptionHandler     : An unexpected connection driver error occured (Exception message: Connection reset)
2018-05-19 12:18:27.816 ERROR 1 --- [172.19.0.4:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 12:18:27.816 ERROR 1 --- [172.19.0.4:5672] o.s.a.r.c.CachingConnectionFactory       : Channel shutdown: connection error
2018-05-19 12:18:28.100  INFO 1 --- [cTaskExecutor-3] o.s.a.r.l.SimpleMessageListenerContainer : Restarting Consumer@5b0307b0: tags=[{amq.ctag-0UhQ6jE-D5Wl2ZPl4EWhDQ=consumer1.queue}], channel=Cached Rabbit Channel: PublisherCallbackChannelImpl: AMQChannel(amqp://admin@172.19.0.4:5672/,1), conn: Proxy@42dd311 Shared Rabbit Connection: SimpleConnection@71dadbb0 [delegate=amqp://admin@172.19.0.4:5672/, localPort= 34416], acknowledgeMode=AUTO local queue size=0
2018-05-19 12:18:28.104  INFO 1 --- [cTaskExecutor-4] o.s.a.r.c.CachingConnectionFactory       : Attempting to connect to: [rabbitmqhost1:5672, rabbitmqhost2:5672, rabbitmqhost3:5672]
2018-05-19 12:19:23.178 ERROR 1 --- [cTaskExecutor-4] o.s.a.r.l.SimpleMessageListenerContainer : Failed to check/redeclare auto-delete queue(s).

org.springframework.amqp.AmqpIOException: java.net.UnknownHostException: rabbitmqhost3
        at org.springframework.amqp.rabbit.support.RabbitExceptionTranslator.convertRabbitAccessException(RabbitExceptionTranslator.java:71) ~[spring-rabbit-2.0.3.RELEASE.jar!/:2.0.3.RELEASE]
        at org.springframework.amqp.rabbit.connection.AbstractConnectionFactory.createBareConnection(AbstractConnectionFactory.java:476) ~[spring-rabbit-2.0.3.RELEASE.jar!/:2.0.3.RELEASE]
        at org.springframework.amqp.rabbit.connection.CachingConnectionFactory.createConnection(CachingConnectionFactory.java:614) ~[spring-rabbit-2.0.3.RELEASE.jar!/:2.0.3.RELEASE]
```
- 如上所示，也是連線失敗，並且，日誌的最後會發現應用在自動嘗試重新連線RabbitMQ；

- 至此，RabbitMQ叢集當機模擬就完成了，結果說明在HA模式下，只要還有可用的節點，應用就會嘗試連線，如果連線成功，訊息的消費是不受影響的；

- 目前RabbitMQ叢集的所有容器都停掉了，接下來我們逐個恢復剛才停下來的容器，看看服務能否恢復；
### 逐個恢復叢集中的RabbitMQ容器

- 先恢復hacluster_rabbit1_1，執行命令**docker start hacluster_rabbit1_1**；
- 執行命令**docker logs -f hacluster_rabbit1_1**，檢視容器日誌，發現一直停留在下面的位置，不再更新：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083739551.png)
- 瀏覽器訪問管理頁面：http://192.168.119.155:15672，結果頁面無法開啟；
- 在瀏覽器輸入：http://192.168.119.155:18080/send/aaa/bbb ，嘗試傳送一條訊息，會顯示報錯頁面；
- 去看生產者和消費者容器的日誌，發現都是連線RabbitMQ失敗的錯誤；
- 從上述現象可以發現：恢復叢集服務時，只恢復一臺機器是不夠的；
- 再恢復hacluster_rabbit2_1，執行命令**docker start hacluster_rabbit12_1**；
- 管理頁面依舊不可用，傳送訊息失敗，並且生產者和消費者容器都無法連線到RabbitMQ容器上去；
- 再恢復hacluster_rabbit3_1，執行命令**docker start hacluster_rabbit3_1**，這樣整個叢集的所有容器都恢復了；
- hacluster_rabbit1_1的日誌發生了變化，如下：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083739637.png)
- hacluster_rabbit2_1的日誌也更新了，如下：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083740000.png)
- 管理頁面可以正常開啟，並且顯示三個節點都正常了：
![這裡寫圖片描述](https://typora-pictures-1253575040.cos.ap-guangzhou.myqcloud.com/70-20220529083740179.png)
- 在瀏覽器輸入：http://192.168.119.155:18080/send/aaa/bbb ，嘗試傳送一條訊息，訊息的生產和消費都正常了；

- 至此，RabbitMQ的高可用實戰已經完成了，從當機到恢復我們都試了一遍，對RabbitMQ叢集也有了更多直觀的瞭解；

- 文章寫到這裡，《Docker下RabbitMQ四部曲》就全部結束了，希望這個系列能夠對您在學習RabbitMQ過程中有所幫助，在docker實戰中，也期待能對您自己定製的RabbitMQ映象提供一些參考；

### 歡迎關注ITpub：程式設計師欣宸
> [學習路上，你不孤單，欣宸原創一路相伴...](http://blog.itpub.net/70017844/)

Docker下RabbitMQ四部曲之四：高可用實戰

相關文章