本文主要是介绍RocketMQ安装、部署(备忘),希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!
RocketMQ
这段时间接触了不少 MQ 产品,印象最为深刻的,当属 RocketMQ
个人认为其架构设计的十分合理
官方地址: https://github.com/apache/rocketmq
使用下来,最开始的安装、部署,遇到不少问题,因此特地备忘下
主要问题均来至 JDK 版本比官方的新
安装相关
官方文档: https://rocketmq.apache.org/docs/quick-start/
安装需求:
64bit OS, Linux/Unix/Mac is recommended;(Windows user see guide below)
64bit JDK 1.8+;
Maven 3.2.x;
Git;
4g+ free disk for Broker server
重点提示:使用 Oracle Java 1.8 ,特别是 OpenJava ,一定会遇到很多问题
官方的快速安装文档: https://github.com/apache/rocketmq/blob/master/docs/cn/dledger/quick_start.md
但是还是不如别人的 docker 来个快, 推荐:
https://github.com/foxiswho/docker-rocketmq
脚本相关
最后附上本人本地部署脚本:
#!/bin/bashROCKETMQ_DATA_DIR=$PWD# 删除
sudo rm -rf $ROCKETMQ_DATA_DIR/data
docker rm -f rocketmq-namesrv
docker rm -f rocketmq-broker1
docker rm -f rocketmq-broker2
docker rm -f rocketmq-broker3
docker rm -f rocketmq-console# 创建目录
mkdir -p ./data/namesrv/logs
mkdir -p ./data/namesrv/store
mkdir -p ./data/broker1/logs
mkdir -p ./data/broker1/store
mkdir -p ./data/broker2/logs
mkdir -p ./data/broker2/store
mkdir -p ./data/broker3/logs
mkdir -p ./data/broker3/store# 设置目录权限
chmod -R 777 ./data/namesrv/logs
chmod -R 777 ./data/namesrv/store
chmod -R 777 ./data/broker1/logs
chmod -R 777 ./data/broker1/store
chmod -R 777 ./data/broker2/logs
chmod -R 777 ./data/broker2/store
chmod -R 777 ./data/broker3/logs
chmod -R 777 ./data/broker3/storedocker run --hostname rocketmq-namesrv --name rocketmq-namesrv \-p 9876:9876 \-d --restart=always \-v $ROCKETMQ_DATA_DIR/data/namesrv/logs:/opt/logs \-v $ROCKETMQ_DATA_DIR/data/namesrv/store:/opt/store \-e JAVA_OPT_EXT="-Duser.home=/opt -Xms512M -Xmx512M -Xmn128m" \foxiswho/rocketmq:4.7.0 sh mqnamesrvdocker run --hostname rocketmq-broker1 --name rocketmq-broker1 \-p 10909:10909 -p 10911:10911 \-d --restart=always \-v $ROCKETMQ_DATA_DIR/data/broker1/logs:/opt/logs \-v $ROCKETMQ_DATA_DIR/data/broker1/store:/opt/store \-v $ROCKETMQ_DATA_DIR/conf/broker1.conf:/etc/rocketmq/broker.conf \-e JAVA_OPT_EXT="-Duser.home=/opt -Xms512M -Xmx512M -Xmn128m" \--link rocketmq-namesrv:rocketmq-namesrv \foxiswho/rocketmq:4.7.0 sh mqbroker -c /etc/rocketmq/broker.conf -n rocketmq-namesrv:9876 autoCreateTopicEnable=truedocker run --hostname rocketmq-broker2 --name rocketmq-broker2 \-p 20909:10909 -p 20911:20911 \-d --restart=always \-v $ROCKETMQ_DATA_DIR/data/broker2/logs:/opt/logs \-v $ROCKETMQ_DATA_DIR/data/broker2/store:/opt/store \-v $ROCKETMQ_DATA_DIR/conf/broker2.conf:/etc/rocketmq/broker.conf \-e JAVA_OPT_EXT="-Duser.home=/opt -Xms512M -Xmx512M -Xmn128m" \--link rocketmq-namesrv:rocketmq-namesrv \foxiswho/rocketmq:4.7.0 sh mqbroker -c /etc/rocketmq/broker.conf -n rocketmq-namesrv:9876 autoCreateTopicEnable=truedocker run --hostname rocketmq-broker3 --name rocketmq-broker3 \-p 30909:10909 -p 30911:30911 \-d --restart=always \-v $ROCKETMQ_DATA_DIR/data/broker3/logs:/opt/logs \-v $ROCKETMQ_DATA_DIR/data/broker3/store:/opt/store \-v $ROCKETMQ_DATA_DIR/conf/broker3.conf:/etc/rocketmq/broker.conf \-e JAVA_OPT_EXT="-Duser.home=/opt -Xms512M -Xmx512M -Xmn128m" \--link rocketmq-namesrv:rocketmq-namesrv \foxiswho/rocketmq:4.7.0 sh mqbroker -c /etc/rocketmq/broker.conf -n rocketmq-namesrv:9876 autoCreateTopicEnable=truedocker run --hostname rocketmq-console --name rocketmq-console \-p 8180:8080 \-e "JAVA_OPTS=-Drocketmq.namesrv.addr=rocketmq-namesrv:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false" \--link rocketmq-namesrv:rocketmq-namesrv \-d --restart=always \pangliang/rocketmq-console-ng# 显示 rocketmq 容器
docker ps | grep rocketmq
broker 的配置文件示例:
#所属集群名字
brokerClusterName=DefaultCluster#broker名字,注意此处不同的配置文件填写的不一样,如果在broker-a.properties使用:broker-a,
#在broker-b.properties使用:broker-b
brokerName=broker-1#0 表示Master,>0 表示Slave
brokerId=0#nameServer地址,分号分割
#namesrvAddr=rocketmq-nameserver1:9876;rocketmq-nameserver2:9876#启动IP,如果 docker 报 com.alibaba.rocketmq.remoting.exception.RemotingConnectException: connect to <192.168.0.120:10909> failed
# 解决方式1 加上一句producer.setVipChannelEnabled(false);,解决方式2 brokerIP1 设置宿主机IP,不要使用docker 内部IP
brokerIP1=172.26.144.19#在发送消息时,自动创建服务器不存在的topic,默认创建的队列数
defaultTopicQueueNums=4#是否允许 Broker 自动创建Topic,建议线下开启,线上关闭 !!!这里仔细看是false,false,false
#原因下篇博客见~ 哈哈哈哈
autoCreateTopicEnable=true#是否允许 Broker 自动创建订阅组,建议线下开启,线上关闭
autoCreateSubscriptionGroup=true#Broker 对外服务的监听端口
listenPort=10911#删除文件时间点,默认凌晨4点
deleteWhen=04#文件保留时间,默认48小时
fileReservedTime=120#commitLog每个文件的大小默认1G
mapedFileSizeCommitLog=1073741824#ConsumeQueue每个文件默认存30W条,根据业务情况调整
mapedFileSizeConsumeQueue=300000#destroyMapedFileIntervalForcibly=120000
#redeleteHangedFileInterval=120000
#检测物理文件磁盘空间
diskMaxUsedSpaceRatio=88
#存储路径
#storePathRootDir=/home/ztztdata/rocketmq-all-4.1.0-incubating/store
#commitLog 存储路径
#storePathCommitLog=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/commitlog
#消费队列存储
#storePathConsumeQueue=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/consumequeue
#消息索引存储路径
#storePathIndex=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/index
#checkpoint 文件存储路径
#storeCheckpoint=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/checkpoint
#abort 文件存储路径
#abortFile=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/abort
#限制的消息大小
maxMessageSize=65536#flushCommitLogLeastPages=4
#flushConsumeQueueLeastPages=2
#flushCommitLogThoroughInterval=10000
#flushConsumeQueueThoroughInterval=60000#Broker 的角色
#- ASYNC_MASTER 异步复制Master
#- SYNC_MASTER 同步双写Master
#- SLAVE
brokerRole=ASYNC_MASTER#刷盘方式
#- ASYNC_FLUSH 异步刷盘
#- SYNC_FLUSH 同步刷盘
flushDiskType=ASYNC_FLUSH#发消息线程池数量
#sendMessageThreadPoolNums=128
#拉消息线程池数量
#pullMessageThreadPoolNums=128
需要注意 2 个配置:
- brokerIP1
- 不填客户端得到的是 docker 内 IP,会造成访问不了
- listenPort
- 不填,集群下,给客户端的都是同个端口
以上
这篇关于RocketMQ安装、部署(备忘)的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!