用两台服务器,搭建出一个双master双slave、无单点故障的高可用 RocketMQ 集群。此处假设两台服务器的物理 IP 分别为:192.168.50.1、192.168.50.2。

内容目录

1. 启动 NameServer 集群

2. 启动 Broker 集群

3. RocketMQ 可视化管理控制台:rocketmq-console

4. 集群测试

1. 启动 NameServer 集群

在两台服务器上分别启动 NameServer,可以得到一个无单点故障的 NameServer 服务,服务地址分别为:192.168.50.1:9876、192.168.50.2:9876。

2. 启动 Broker 集群

修改 Broker 配置文件,以使每台服务器上都可以启动一个 Master 角色 的 Broker 和 一个Slave 角色的 Broker。
首先找到 Broker 配置文件,此处我们搭建一个同步双写模式的集群,所以需要修改 2m-2s-sync 目录下的 broker 配置文件:

[root@- ~]# cd /usr/local/rocketmq-all-4.3.-bin-release/conf/
[root@- conf]# ls
2m-2s-async 2m-2s-sync 2m-noslave broker.conf logback_broker.xml logback_namesrv.xml logback_tools.xml
[root@- conf]# cd 2m-2s-sync/
[root@- 2m-2s-sync]# ls
broker-a.properties broker-a-s.properties broker-b.properties broker-b-s.properties

1) 修改 192.168.50.1 服务器上的 broker-a.properties 为 Master 角色的 Broker:

namesrvAddr=192.168.50.1:;192.168.50.2:
brokerClusterName=rocketMqCluster
brokerIP1=192.168.50.1
brokerName=broker-a
brokerId=
deleteWhen=
fileReservedTime=
mapedFileSizeConsumeQueue=
brokerRole=SYNC_MASTER
flushDiskType=ASYNC_FLUSH
listenPort=
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
storePathRootDir=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a
storePathCommitLog=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a/commitlog
storePathConsumeQueue=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a/consumequeue
storePathIndex=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a/index
storeCheckpoint=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a/checkpoint
abortFile=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a/abort

2) 修改 192.168.50.2 服务器上的 broker-b.properties 为 Master 角色的 Broker:

namesrvAddr=192.168.50.1:;192.168.50.2:
brokerClusterName=rocketMqCluster
brokerIP1=192.168.50.2
brokerName=broker-b
brokerId=
deleteWhen=
fileReservedTime=
mapedFileSizeConsumeQueue=
brokerRole=SYNC_MASTER
flushDiskType=ASYNC_FLUSH
listenPort=
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
storePathRootDir=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b
storePathCommitLog=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b/commitlog
storePathConsumeQueue=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b/consumequeue
storePathIndex=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b/index
storeCheckpoint=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b/checkpoint
abortFile=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b/abort

3) 修改 192.168.50.1 服务器上的 broker-b-s.properties 为 Slave 角色的 Broker:

namesrvAddr=192.168.50.1:;192.168.50.2:
brokerClusterName=rocketMqCluster
brokerIP1=192.168.50.1
brokerName=broker-b
brokerId=
deleteWhen=
fileReservedTime=
mapedFileSizeConsumeQueue=
brokerRole=SLAVE
flushDiskType=ASYNC_FLUSH
listenPort=
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
storePathRootDir=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b-s
storePathCommitLog=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b-s/commitlog
storePathConsumeQueue=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b-s/consumequeue
storePathIndex=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b-s/index
storeCheckpoint=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b-s/checkpoint
abortFile=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-b-s/abort

4) 修改 192.168.50.2 服务器上的 broker-a-s.properties 为 Slave 角色的 Broker:

namesrvAddr=192.168.50.1:;192.168.50.2:
brokerClusterName=rocketMqCluster
brokerIP1=192.168.50.2
brokerName=broker-a
brokerId=
deleteWhen=
fileReservedTime=
brokerRole=SLAVE
flushDiskType=ASYNC_FLUSH
listenPort=
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
storePathRootDir=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a-s
storePathCommitLog=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a-s/commitlog
storePathConsumeQueue=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a-s/consumequeue
storePathIndex=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a-s/index
storeCheckpoint=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a-s/checkpoint
abortFile=/usr/local/rocketmq-all-4.3.-bin-release/data/broker-a-s/abort

一台服务器上启动多个Broker 时,需指定不同的端口号,记得防火墙放开 NameServer 和 Broker 中用到的端口号哦~

分别启动四个 Broker:

nohup sh bin/mqbroker -c broker_config_file &

3. RocketMQ 可视化管理控制台:rocketmq-console

在服务器 192.168.50.1 上安装即可,无需集群

[root@- local]# git clone https://github.com/apache/rocketmq-externals.git
Cloning into 'rocketmq-externals'...
remote: Enumerating objects: , done.
remote: Counting objects: % (/), done.
remote: Compressing objects: % (/), done.
remote: Total (delta ), reused (delta ), pack-reused
Receiving objects: % (/), 11.86 MiB | 232.00 KiB/s, done.
Resolving deltas: % (/), done.
[root@- local]# cd rocketmq-externals/
[root@- rocketmq-externals]# ls
dev README.md rocketmq-console rocketmq-docker rocketmq-flink rocketmq-flume rocketmq-hbase rocketmq-iot-bridge rocketmq-jms rocketmq-mysql rocketmq-php rocketmq-redis rocketmq-sentinel rocketmq-serializer rocketmq-spark
[root@- rocketmq-externals]# git branch
* master
[root@- rocketmq-externals]# git fetch origin release-rocketmq-console-1.0.
From https://github.com/apache/rocketmq-externals
* branch release-rocketmq-console-1.0. -> FETCH_HEAD
[root@- rocketmq-externals]# git checkout -b release-1.0. origin/release-rocketmq-console-1.0.
Branch 'release-1.0.0' set up to track remote branch 'release-rocketmq-console-1.0.0' from 'origin'.
Switched to a new branch 'release-1.0.0'
[root@- rocketmq-externals]# ls
README.md rocketmq-console
[root@- rocketmq-externals]# ls rocketmq-console/
doc LICENSE NOTICE pom.xml README.md src style
[root@- rocketmq-externals]# vim rocketmq-console/src/main/resources/application.properties

编辑 application.properties:

server.contextPath=/rocketmq
server.port=
#spring.application.index=true
spring.application.name=rocketmq-console
spring.http.encoding.charset=UTF-
spring.http.encoding.enabled=true
spring.http.encoding.force=true
logging.config=classpath:logback.xml
#if this value is empty,use env value rocketmq.config.namesrvAddr NAMESRV_ADDR | now, you can set it in ops page.default localhost:9876
rocketmq.config.namesrvAddr=192.168.50.1:;192.168.50.2:
#if you use rocketmq version < 3.5.8, rocketmq.config.isVIPChannel should be false.default true
rocketmq.config.isVIPChannel=
#rocketmq-console's data path:dashboard/monitor
rocketmq.config.dataPath=/tmp/rocketmq-console/data
#set it false if you don't want use dashboard.default true
rocketmq.config.enableDashBoardCollect=true

移动 rocketmq-console 所在目录,编译并启动 rocketmq-console:

[root@- rocketmq-console]# mv /usr/local/rocketmq-externals/rocketmq-console /usr/local/rocketmq-console
[root@- rocketmq-console]# cd /usr/local/rocketmq-console/
[root@- rocketmq-console]# ls
doc LICENSE NOTICE pom.xml README.md src style
[root@- rocketmq-console]# mvn clean package -Dmaven.test.skip=true
........
[INFO] Building jar: /usr/local/rocketmq-console/target/rocketmq-console-ng-1.0.-sources.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: : min
[INFO] Finished at: --11T17::+:
[INFO] ------------------------------------------------------------------------
[root@- rocketmq-console]# ls
doc LICENSE NOTICE pom.xml README.md src style target
[root@- rocketmq-console]# ls target/
checkstyle-cachefile checkstyle-checker.xml checkstyle-result.xml classes generated-sources maven-archiver maven-status rocketmq-console-ng-1.0..jar rocketmq-console-ng-1.0..jar.original rocketmq-console-ng-1.0.-sources.jar
[root@- rocketmq-console]# java -jar target/rocketmq-console-ng-1.0..jar
.......
[-- ::15.980] INFO Initializing ProtocolHandler ["http-nio-8080"]
[-- ::15.991] INFO Starting ProtocolHandler [http-nio-]
[-- ::16.232] INFO Using a shared selector for servlet write/read
[-- ::16.251] INFO Tomcat started on port(s): (http)
[-- ::16.257] INFO Started App in 6.594 seconds (JVM running for 7.239)

4. 集群测试

Producer 测试代码:

public class SyncProducerTest {
public static void main(String[] args) {
DefaultMQProducer producer = new DefaultMQProducer("producer_test_group");
producer.setNamesrvAddr("39.107.153.215:9876;39.107.157.89:9876");
try{
producer.start();
for(int i=0;i<100;i++){
Message message = new Message("topic_test", "tag_test", ("Hello World" + 1).getBytes("UTF-8"));
SendResult sendResult = producer.send(message);
System.out.println(JSON.toJSON(sendResult));
}
producer.shutdown();
}catch (Exception e){
e.printStackTrace();
}
}
}

Consumer 测试代码:

public class SyncConsumerTest {
public static void main(String[] args) {
DefaultMQPushConsumer consumer = new DefaultMQPushConsumer("consumer_test_group");
consumer.setNamesrvAddr("39.107.153.215:9876;39.107.157.89:9876");
consumer.setConsumeFromWhere(ConsumeFromWhere.CONSUME_FROM_FIRST_OFFSET);
try {
consumer.subscribe("topic_test", "*");
consumer.registerMessageListener((MessageListenerConcurrently) (messageList, context) -> {
System.out.println(Thread.currentThread().getName() + " Receive New Message:" + messageList);
return ConsumeConcurrentlyStatus.CONSUME_SUCCESS;
});
consumer.start();
}catch (Exception e){
e.printStackTrace();
}
}
}

SyncProducerTest 运行日志:

SyncConsumerTest 运行日志:

通过日志可以看到,消费者、生产者收发消息都是正常的,我们去可视化管理控制台查看下 http://192.168.50.1:8080/rocketmq:

通过管控台可以看到,双 master 双 slave 的 broker 集群一切正常,并可进一步看到每个 broker 处理消息的情况。

最新文章

  1. 虚拟文件系统(VFS)
  2. @Resource、@Autowired、@Qualifier的注解注入及区别
  3. Js之AJAX
  4. C++中const 的各种用法
  5. Swift基础语法学习总结
  6. jQuery的无new实例化
  7. 【leetcode❤python】409. Longest Palindrome
  8. PHP5 session 详解
  9. cocos2d-x3.9 NDK android 环境搭建过程中遇到的错误
  10. YII CJson类
  11. 人工智能2:智能Agent
  12. c# windows服务 一个项目安装多个服务
  13. SpringMVC拦截器和过滤器
  14. 增加tomcat的缓存
  15. AI 强化学习
  16. Android 自定义类型文件与程序关联
  17. T分布在医药领域应用-python建模
  18. VMware vmdk文件打开方法
  19. .NET零基础入门05:委托与事件
  20. 日志收集以及分析:Splunk

热门文章

  1. OO第三单元总结--根据JML写代码
  2. Oracle Spatial中的空间索引
  3. SqlSugar最容易使用的ORM
  4. 地球Gauss_Kruger中央0度经线图
  5. BZOJ 1091([SCOI2003]分割多边形-分割直线)
  6. python菜鸟日记1
  7. SQL2012 尝试读取或写入受保护的内存。这通常指示其它内存已损坏
  8. [原创+分享]Mandelbrot Explorer
  9. Make 编译脚本上手
  10. 链接脚本在编程中的高级运用之二——执行时库和C++特性支持