一. 传统安装

  1. 下载RocketMQ到Linux服务器里

rocketmq-all-4.7.1-bin-release.zip

  1. 解压

    1. unzip rocketmq-all-4.7.1-bin-release.zip

  2. 启动NameServer

    1. cd rocketmq-all-4.7.1-bin-release
    2. nohup ./bin/mqnamesrv &

    PS: 若你的服务器内存太小会直接报错！
    image.png

查看nohup.out可知问题，分配的内存不够
image.png

  1. 修改JVM参数
    1. vim bin/runserver.sh
    2. vim bin/runbroker.sh
    这里我更改的比较小，根据实际情况变更哦
    image.png

启动namesrv服务：nohup sh bin/mqnamesrv &
启动broker服务：nohup sh bin/mqbroker &

关闭namesrv服务：sh bin/mqshutdown namesrv
关闭broker服务 ：sh bin/mqshutdown broker

查看日志：tailf ~/logs/rocketmqlogs/namesrv.log
查看日志：tailf ~/logs/rocketmqlogs/broker.log
[

](https://blog.csdn.net/www_wangzheguilai/article/details/76483705)

二. 使用dokcer部署（推荐）

1. 使用docker服务部署搭配docker-compose一键快速部署

  1. cd /usr/local/docker/rocketmq   #若没有对应目录自行创建
  2. vim docker-compose.yml

docker-compose.yml

  1. version: '3.5'
  2. services:
  3.   rmqnamesrv:
  4.     image: foxiswho/rocketmq:server
  5.     container_name: rmqnamesrv
  6.     ports:
  7.       - 9876:9876
  8.     volumes:
  9.       - ./data/logs:/opt/logs
  10.       - ./data/store:/opt/store
  11.     networks:
  12.         rmq:
  13.           aliases:
  14.             - rmqnamesrv
  16.   rmqbroker:
  17.     image: foxiswho/rocketmq:broker
  18.     container_name: rmqbroker
  19.     ports:
  20.       - 10909:10909
  21.       - 10911:10911
  22.     volumes:
  23.       - ./data/logs:/opt/logs
  24.       - ./data/store:/opt/store
  25.       - ./data/brokerconf/broker.conf:/etc/rocketmq/broker.conf
  26.     environment:
  27.         NAMESRV_ADDR: "rmqnamesrv:9876"
  28.         JAVA_OPTS: " -Duser.home=/opt"
  29.         JAVA_OPT_EXT: "-server -Xms128m -Xmx128m -Xmn128m"
  30.     command: mqbroker -c /etc/rocketmq/broker.conf
  31.     depends_on:
  32.       - rmqnamesrv
  33.     networks:
  34.       rmq:
  35.         aliases:
  36.           - rmqbroker
  38.   rmqconsole:
  39.     image: styletang/rocketmq-console-ng
  40.     container_name: rmqconsole
  41.     ports:
  42.       - 8080:8080
  43.     environment:
  44.         JAVA_OPTS: "-Drocketmq.namesrv.addr=rmqnamesrv:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false"
  45.     depends_on:
  46.       - rmqnamesrv
  47.     networks:
  48.       rmq:
  49.         aliases:
  50.           - rmqconsole
  52. networks:
  53.   rmq:
  54.     name: rmq
  55.     driver: bridge

保存退出,接着

  1. mkdir data
  2. cd data/
  3. mkdir brokerconf
  4. cd brokerconf/
  5. vim broker.conf

broker.conf

  1. # Licensed to the Apache Software Foundation (ASF) under one or more
  2. # contributor license agreements.  See the NOTICE file distributed with
  3. # this work for additional information regarding copyright ownership.
  4. # The ASF licenses this file to You under the Apache License, Version 2.0
  5. # (the "License"); you may not use this file except in compliance with
  6. # the License.  You may obtain a copy of the License at
  7. #
  8. #     http://www.apache.org/licenses/LICENSE-2.0
  9. #
  10. #  Unless required by applicable law or agreed to in writing, software
  11. #  distributed under the License is distributed on an "AS IS" BASIS,
  12. #  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  13. #  See the License for the specific language governing permissions and
  14. #  limitations under the License.
  17. # 所属集群名字
  18. brokerClusterName=DefaultCluster
  20. # broker 名字，注意此处不同的配置文件填写的不一样，如果在 broker-a.properties 使用: broker-a,
  21. # 在 broker-b.properties 使用: broker-b
  22. brokerName=broker-a
  24. # 0 表示 Master，> 0 表示 Slave
  25. brokerId=0
  27. # nameServer地址，分号分割
  28. # namesrvAddr=rocketmq-nameserver1:9876;rocketmq-nameserver2:9876
  30. # 启动IP,如果 docker 报 com.alibaba.rocketmq.remoting.exception.RemotingConnectException: connect to <192.168.0.120:10909> failed
  31. # 解决方式1 加上一句 producer.setVipChannelEnabled(false);，解决方式2 brokerIP1 设置宿主机IP，不要使用docker 内部IP
  32. brokerIP1=192.168.0.253（你自己宿主机的IP，请参考自己）
  34. # 在发送消息时，自动创建服务器不存在的topic，默认创建的队列数
  35. defaultTopicQueueNums=4
  37. # 是否允许 Broker 自动创建 Topic，建议线下开启，线上关闭 ！！！这里仔细看是 false，false，false
  38. autoCreateTopicEnable=true
  40. # 是否允许 Broker 自动创建订阅组，建议线下开启，线上关闭
  41. autoCreateSubscriptionGroup=true
  43. # Broker 对外服务的监听端口
  44. listenPort=10911
  46. # 删除文件时间点，默认凌晨4点
  47. deleteWhen=04
  49. # 文件保留时间，默认48小时
  50. fileReservedTime=120
  52. # commitLog 每个文件的大小默认1G
  53. mapedFileSizeCommitLog=1073741824
  55. # ConsumeQueue 每个文件默认存 30W 条，根据业务情况调整
  56. mapedFileSizeConsumeQueue=300000
  58. # destroyMapedFileIntervalForcibly=120000
  59. # redeleteHangedFileInterval=120000
  60. # 检测物理文件磁盘空间
  61. diskMaxUsedSpaceRatio=88
  62. # 存储路径
  63. # storePathRootDir=/home/ztztdata/rocketmq-all-4.1.0-incubating/store
  64. # commitLog 存储路径
  65. # storePathCommitLog=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/commitlog
  66. # 消费队列存储
  67. # storePathConsumeQueue=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/consumequeue
  68. # 消息索引存储路径
  69. # storePathIndex=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/index
  70. # checkpoint 文件存储路径
  71. # storeCheckpoint=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/checkpoint
  72. # abort 文件存储路径
  73. # abortFile=/home/ztztdata/rocketmq-all-4.1.0-incubating/store/abort
  74. # 限制的消息大小
  75. maxMessageSize=65536
  77. # flushCommitLogLeastPages=4
  78. # flushConsumeQueueLeastPages=2
  79. # flushCommitLogThoroughInterval=10000
  80. # flushConsumeQueueThoroughInterval=60000
  82. # Broker 的角色
  83. # - ASYNC_MASTER 异步复制Master
  84. # - SYNC_MASTER 同步双写Master
  85. # - SLAVE
  86. brokerRole=ASYNC_MASTER
  88. # 刷盘方式
  89. # - ASYNC_FLUSH 异步刷盘
  90. # - SYNC_FLUSH 同步刷盘
  91. flushDiskType=ASYNC_FLUSH
  93. # 发消息线程池数量
  94. # sendMessageThreadPoolNums=128
  95. # 拉消息线程池数量
  96. # pullMessageThreadPoolNums=128

注意：brokerIP1要改成自己的IP，并且对外放出所有端口

回到docker-compose.yml路径下，运行启动docker-compose

  1. cd ../../
  2. docker-compose up -d
  3. docker ps #查看是否运行

成功如下
image.png
在portain中可以查看到容器状态image.png

2. 查看RocketMQ控制台

访问 http://RocketMQIP:8080 登入控制台
image.png

这样环境就搭建好了，结合springboot测试demo请看RocketMQ在Springbot上测试