【RockerMq】Docker创建Rocketmq

1.rocketmq

• https://hub.docker.com/r/apache/rocketmq/tags
  
• 拉取apache的这个包

docker pull apache/rocketmq:4.9.3

docker run -d \
--restart=always \
--name rocketmq \
-p 9876:9876 \
-v /data/home/hfg/Soft/rocketmq/logs:/root/logs \
-v /data/home/hfg/Soft/rocketmq/store:/root/store \
-e "MAX_POSSIBLE_HEAP=100000000" \
apache/rocketmq:4.9.3 \
sh mqnamesrv  autoCreateTopicEnable=true

2.rocketmq-broker

• 创建目录

mkdir -p  /data/home/hfg/Soft/rocketmq/data/broker/logs \
/data/home/hfg/Soft/rocketmq/data/broker/store \
/data/home/hfg/Soft/rocketmq/conf

• 执行vim

vim /data/home/hfg/Soft/rocketmq/conf/broker.conf

• 将一下内容粘贴进去，修改对应的ip，brokerip为当前部署的ip

# 所属集群名称，如果节点较多可以配置多个
brokerClusterName = DefaultCluster
#broker名称，master和slave使用相同的名称，表明他们的主从关系
brokerName = broker-a
#0表示Master，大于0表示不同的slave
brokerId = 0
#表示几点做消息删除动作，默认是凌晨4点
deleteWhen = 04
#在磁盘上保留消息的时长，单位是小时
fileReservedTime = 48
#有三个值：SYNC_MASTER，ASYNC_MASTER，SLAVE；同步和异步表示Master和Slave之间同步数据的机制；
brokerRole = ASYNC_MASTER
#刷盘策略，取值为：ASYNC_FLUSH，SYNC_FLUSH表示同步刷盘和异步刷盘；SYNC_FLUSH消息写入磁盘后才返回成功状态，ASYNC_FLUSH不需要；
flushDiskType = ASYNC_FLUSH
# 设置broker节点所在服务器的ip地址
brokerIP1 = 192.168.124.1
# 磁盘使用达到95%之后,生产者再写入消息会报错 CODE: 14 DESC: service not available now, maybe disk full

docker run -d  \
--restart=always \
--name rmqbroker \
--link rocketmq:namesrv \
-p 10911:10911 \
-p 10909:10909 \
-v  /data/home/hfg/Soft/rocketmq/data/broker/logs:/root/logs \
-v  /data/home/hfg/Soft/rocketmq/data/broker/store:/root/store \
-v /data/home/hfg/Soft/rocketmq/conf/broker.conf:/opt/rocketmq-4.4.0/conf/broker.conf \
-e "NAMESRV_ADDR=namesrv:9876" \
-e "MAX_POSSIBLE_HEAP=200000000" \
rocketmqinc/rocketmq \
sh mqbroker -c /opt/rocketmq-4.4.0/conf/broker.conf 

3. console

• 拉取 console镜像

docker pull pangliang/rocketmq-console-ng

• 执行替换自己的ip地址

docker run -d \
--restart=always \
--name rmqadmin \
-e "JAVA_OPTS=-Drocketmq.namesrv.addr=192.168.124.121:9876 \
-Dcom.rocketmq.sendMessageWithVIPChannel=false" \
-p 9999:8080 \
pangliang/rocketmq-console-ng

• 当控制台出现如图就说明没问题了