From 3fb63664bb6622574ca2f3021a1c04e5b1581382 Mon Sep 17 00:00:00 2001 From: Odboy Date: Sat, 14 Nov 2026 21:45:49 +0800 Subject: [PATCH] =?UTF-8?q?feat:=20rocketmq=205.5.0=20=E8=A1=A5=E5=85=85?= =?UTF-8?q?=E6=96=B0=E7=89=B9=E6=80=A7=E9=85=8D=E7=BD=AE=EF=BC=88Lite=20Mo?= =?UTF-8?q?de/LMQ/Controller/RocksDB=EF=BC=89=E4=B8=8E=20namesrv.conf?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../broker-master/broker.conf | 63 ++++++++++++++++++- .../broker-slave1/broker.conf | 63 ++++++++++++++++++- .../broker-slave2/broker.conf | 63 ++++++++++++++++++- .../docker-compose.yml | 44 +++++-------- .../namesrv/conf/namesrv.conf | 36 +++++++++++ .../broker-master1/broker.conf | 63 ++++++++++++++++++- .../broker-master2/broker.conf | 63 ++++++++++++++++++- .../docker-compose.yml | 37 +++++------ .../namesrv/conf/namesrv.conf | 36 +++++++++++ .../docker-compose.yml | 30 ++++----- .../master/broker.conf | 63 ++++++++++++++++++- .../namesrv/conf/namesrv.conf | 36 +++++++++++ 12 files changed, 513 insertions(+), 84 deletions(-) create mode 100644 deploy/rocketmq-5.5.0-cluster-1m2s/namesrv/conf/namesrv.conf create mode 100644 deploy/rocketmq-5.5.0-cluster-2m/namesrv/conf/namesrv.conf create mode 100644 deploy/rocketmq-5.5.0-standalone/namesrv/conf/namesrv.conf diff --git a/deploy/rocketmq-5.5.0-cluster-1m2s/broker-master/broker.conf b/deploy/rocketmq-5.5.0-cluster-1m2s/broker-master/broker.conf index 3d64d68..ea5f100 100644 --- a/deploy/rocketmq-5.5.0-cluster-1m2s/broker-master/broker.conf +++ b/deploy/rocketmq-5.5.0-cluster-1m2s/broker-master/broker.conf @@ -1,5 +1,5 @@ namesrvAddr=rmqnamesrv:9876 -brokerIP1=172.21.0.81 +brokerIP1=172.20.0.81 brokerName=rmqbroker1 brokerClusterName=rmqbroker brokerId=0 @@ -7,8 +7,8 @@ autoCreateTopicEnable=false autoCreateSubscriptionGroup=true rejectTransactionMessage=false fetchNamesrvAddrByAddressServer=false -storePathRootDir=/home/rocketmq/rocketmq-5.5.0/store -storePathCommitLog=/home/rocketmq/rocketmq-5.5.0/store/commitlog +storePathRootDir=/home/rocketmq/rocketmq-4.9.7/store +storePathCommitLog=/home/rocketmq/rocketmq-4.9.7/store/commitlog flushIntervalCommitLog=1000 flushCommitLogTimed=false deleteWhen=04 @@ -24,3 +24,60 @@ haMasterAddress= brokerRole=ASYNC_MASTER flushDiskType=ASYNC_FLUSH cleanFileForciblyEnable=true + +# ===================== RocketMQ 5.5.0 新特性(显式写出默认值,便于检索与调参) ===================== + +# ---- Lite Mode(RIP-83,5.5.0 唯一新增特性):面向 AI 场景的轻量级订阅模型 ---- +# 开关 Lite 事件分发,Lite Topic 的生命周期管理、订阅注册、指标上报都依赖它,默认 true +enableLiteEventMode=true +# Lite 事件分发扫描周期,单位毫秒;越小越实时,越大越省 CPU,默认 10000 +liteEventCheckInterval=10000 +# Lite Topic 过期检查周期,单位毫秒,默认 120000 +liteTtlCheckInterval=120000 +# Lite Topic 最短存活时间,单位毫秒,默认 900000(15 分钟),存活不足该时长的 Topic 不会被清理 +minLiteTTl=900000 +# Lite 订阅有效性检查周期,单位毫秒,默认 120000 +liteSubscriptionCheckInterval=120000 +# Lite 订阅检查超时时间,单位毫秒,默认 180000 +liteSubscriptionCheckTimeoutMills=180000 +# 单个 Broker 允许的 Lite 订阅数量上限,默认 100000 +maxLiteSubscriptionCount=100000 +# 是否打印 Lite POP 消费日志,排查 Lite 问题时临时置 true,默认 false +enableLitePopLog=false +# 单个 Lite 客户端连接允许挂载的最大事件数,默认 100 +maxClientEventCount=100 +# 全量分发延迟时间,单位毫秒,默认 10000,避免订阅建立瞬间的抖动 +liteEventFullDispatchDelayTime=10000 +# 通配订阅(wildcard group)的全量分发延迟时间,单位毫秒,默认 10000 +liteEventFullDispatchDelayTimeForWildcardGroup=10000 +# Lite 消费延迟指标:是否采集 storeTime(有额外开销),默认 false +liteLagLatencyCollectEnable=false +# 是否开启 Lite 消费延迟指标,默认 false +liteLagLatencyMetricsEnable=false +# 是否开启 Lite 堆积条数指标,默认 false +liteLagCountMetricsEnable=false +# Lite 延迟指标只统计 TopK,默认 50 +liteLagLatencyTopK=50 + +# ---- Light Message Queue(LMQ,5.x 轻量消息队列,Lite Mode 的存储底座之一)---- +# 是否启用 LMQ,启用后每个队列可承载大量轻量消息,默认 false;需要配合 Lite 使用时再打开 +enableLmq=false +# 是否启用 LMQ 配额控制,默认 false +enableLmqQuota=false + +# ---- Controller 模式(5.x 主从自动切换)---- +# 是否以 Controller 模式启动 Broker(自动选主,替代人工主从切换),默认 false +# 注意:开启后必须同时运行 controller 组件(namesrv 内嵌 controller 或独立 controller 服务),否则 Broker 选不出主节点 +enableControllerMode=false +# Controller 地址列表,多个地址用分号分隔;仅在 enableControllerMode=true 时生效 +controllerAddr= + +# ---- RocksDB 存储增强(5.x 默认存储后端,4.x 无)---- +# 事务消息是否使用 RocksDB 存储(半消息/op 消息),默认 false +transRocksDBEnable=false +# 启用 transRocksDBEnable 后,是否仍把原始半消息写入 CommitLog,默认 true +transWriteOriginTransHalfEnable=true + +# ---- 其它 5.x 才有的能力 ---- +# 是否开启 ConsumeQueue 扩展存储(存放消息 TAG 的哈希等),按需开启,默认 false +enableConsumeQueueExt=false diff --git a/deploy/rocketmq-5.5.0-cluster-1m2s/broker-slave1/broker.conf b/deploy/rocketmq-5.5.0-cluster-1m2s/broker-slave1/broker.conf index 7f54ed9..cb15128 100644 --- a/deploy/rocketmq-5.5.0-cluster-1m2s/broker-slave1/broker.conf +++ b/deploy/rocketmq-5.5.0-cluster-1m2s/broker-slave1/broker.conf @@ -1,5 +1,5 @@ namesrvAddr=rmqnamesrv:9876 -brokerIP1=172.21.0.82 +brokerIP1=172.20.0.82 brokerName=rmqbroker2 brokerClusterName=rmqbroker brokerId=1 @@ -7,8 +7,8 @@ autoCreateTopicEnable=false autoCreateSubscriptionGroup=true rejectTransactionMessage=false fetchNamesrvAddrByAddressServer=false -storePathRootDir=/home/rocketmq/rocketmq-5.5.0/store -storePathCommitLog=/home/rocketmq/rocketmq-5.5.0/store/commitlog +storePathRootDir=/home/rocketmq/rocketmq-4.9.7/store +storePathCommitLog=/home/rocketmq/rocketmq-4.9.7/store/commitlog flushIntervalCommitLog=1000 flushCommitLogTimed=false deleteWhen=04 @@ -24,3 +24,60 @@ haMasterAddress= brokerRole=SLAVE flushDiskType=ASYNC_FLUSH cleanFileForciblyEnable=true + +# ===================== RocketMQ 5.5.0 新特性(显式写出默认值,便于检索与调参) ===================== + +# ---- Lite Mode(RIP-83,5.5.0 唯一新增特性):面向 AI 场景的轻量级订阅模型 ---- +# 开关 Lite 事件分发,Lite Topic 的生命周期管理、订阅注册、指标上报都依赖它,默认 true +enableLiteEventMode=true +# Lite 事件分发扫描周期,单位毫秒;越小越实时,越大越省 CPU,默认 10000 +liteEventCheckInterval=10000 +# Lite Topic 过期检查周期,单位毫秒,默认 120000 +liteTtlCheckInterval=120000 +# Lite Topic 最短存活时间,单位毫秒,默认 900000(15 分钟),存活不足该时长的 Topic 不会被清理 +minLiteTTl=900000 +# Lite 订阅有效性检查周期,单位毫秒,默认 120000 +liteSubscriptionCheckInterval=120000 +# Lite 订阅检查超时时间,单位毫秒,默认 180000 +liteSubscriptionCheckTimeoutMills=180000 +# 单个 Broker 允许的 Lite 订阅数量上限,默认 100000 +maxLiteSubscriptionCount=100000 +# 是否打印 Lite POP 消费日志,排查 Lite 问题时临时置 true,默认 false +enableLitePopLog=false +# 单个 Lite 客户端连接允许挂载的最大事件数,默认 100 +maxClientEventCount=100 +# 全量分发延迟时间,单位毫秒,默认 10000,避免订阅建立瞬间的抖动 +liteEventFullDispatchDelayTime=10000 +# 通配订阅(wildcard group)的全量分发延迟时间,单位毫秒,默认 10000 +liteEventFullDispatchDelayTimeForWildcardGroup=10000 +# Lite 消费延迟指标:是否采集 storeTime(有额外开销),默认 false +liteLagLatencyCollectEnable=false +# 是否开启 Lite 消费延迟指标,默认 false +liteLagLatencyMetricsEnable=false +# 是否开启 Lite 堆积条数指标,默认 false +liteLagCountMetricsEnable=false +# Lite 延迟指标只统计 TopK,默认 50 +liteLagLatencyTopK=50 + +# ---- Light Message Queue(LMQ,5.x 轻量消息队列,Lite Mode 的存储底座之一)---- +# 是否启用 LMQ,启用后每个队列可承载大量轻量消息,默认 false;需要配合 Lite 使用时再打开 +enableLmq=false +# 是否启用 LMQ 配额控制,默认 false +enableLmqQuota=false + +# ---- Controller 模式(5.x 主从自动切换)---- +# 是否以 Controller 模式启动 Broker(自动选主,替代人工主从切换),默认 false +# 注意:开启后必须同时运行 controller 组件(namesrv 内嵌 controller 或独立 controller 服务),否则 Broker 选不出主节点 +enableControllerMode=false +# Controller 地址列表,多个地址用分号分隔;仅在 enableControllerMode=true 时生效 +controllerAddr= + +# ---- RocksDB 存储增强(5.x 默认存储后端,4.x 无)---- +# 事务消息是否使用 RocksDB 存储(半消息/op 消息),默认 false +transRocksDBEnable=false +# 启用 transRocksDBEnable 后,是否仍把原始半消息写入 CommitLog,默认 true +transWriteOriginTransHalfEnable=true + +# ---- 其它 5.x 才有的能力 ---- +# 是否开启 ConsumeQueue 扩展存储(存放消息 TAG 的哈希等),按需开启,默认 false +enableConsumeQueueExt=false diff --git a/deploy/rocketmq-5.5.0-cluster-1m2s/broker-slave2/broker.conf b/deploy/rocketmq-5.5.0-cluster-1m2s/broker-slave2/broker.conf index 018f393..6e35544 100644 --- a/deploy/rocketmq-5.5.0-cluster-1m2s/broker-slave2/broker.conf +++ b/deploy/rocketmq-5.5.0-cluster-1m2s/broker-slave2/broker.conf @@ -1,5 +1,5 @@ namesrvAddr=rmqnamesrv:9876 -brokerIP1=172.21.0.83 +brokerIP1=172.20.0.83 brokerName=rmqbroker3 brokerClusterName=rmqbroker brokerId=2 @@ -7,8 +7,8 @@ autoCreateTopicEnable=false autoCreateSubscriptionGroup=true rejectTransactionMessage=false fetchNamesrvAddrByAddressServer=false -storePathRootDir=/home/rocketmq/rocketmq-5.5.0/store -storePathCommitLog=/home/rocketmq/rocketmq-5.5.0/store/commitlog +storePathRootDir=/home/rocketmq/rocketmq-4.9.7/store +storePathCommitLog=/home/rocketmq/rocketmq-4.9.7/store/commitlog flushIntervalCommitLog=1000 flushCommitLogTimed=false deleteWhen=04 @@ -24,3 +24,60 @@ haMasterAddress= brokerRole=SLAVE flushDiskType=ASYNC_FLUSH cleanFileForciblyEnable=true + +# ===================== RocketMQ 5.5.0 新特性(显式写出默认值,便于检索与调参) ===================== + +# ---- Lite Mode(RIP-83,5.5.0 唯一新增特性):面向 AI 场景的轻量级订阅模型 ---- +# 开关 Lite 事件分发,Lite Topic 的生命周期管理、订阅注册、指标上报都依赖它,默认 true +enableLiteEventMode=true +# Lite 事件分发扫描周期,单位毫秒;越小越实时,越大越省 CPU,默认 10000 +liteEventCheckInterval=10000 +# Lite Topic 过期检查周期,单位毫秒,默认 120000 +liteTtlCheckInterval=120000 +# Lite Topic 最短存活时间,单位毫秒,默认 900000(15 分钟),存活不足该时长的 Topic 不会被清理 +minLiteTTl=900000 +# Lite 订阅有效性检查周期,单位毫秒,默认 120000 +liteSubscriptionCheckInterval=120000 +# Lite 订阅检查超时时间,单位毫秒,默认 180000 +liteSubscriptionCheckTimeoutMills=180000 +# 单个 Broker 允许的 Lite 订阅数量上限,默认 100000 +maxLiteSubscriptionCount=100000 +# 是否打印 Lite POP 消费日志,排查 Lite 问题时临时置 true,默认 false +enableLitePopLog=false +# 单个 Lite 客户端连接允许挂载的最大事件数,默认 100 +maxClientEventCount=100 +# 全量分发延迟时间,单位毫秒,默认 10000,避免订阅建立瞬间的抖动 +liteEventFullDispatchDelayTime=10000 +# 通配订阅(wildcard group)的全量分发延迟时间,单位毫秒,默认 10000 +liteEventFullDispatchDelayTimeForWildcardGroup=10000 +# Lite 消费延迟指标:是否采集 storeTime(有额外开销),默认 false +liteLagLatencyCollectEnable=false +# 是否开启 Lite 消费延迟指标,默认 false +liteLagLatencyMetricsEnable=false +# 是否开启 Lite 堆积条数指标,默认 false +liteLagCountMetricsEnable=false +# Lite 延迟指标只统计 TopK,默认 50 +liteLagLatencyTopK=50 + +# ---- Light Message Queue(LMQ,5.x 轻量消息队列,Lite Mode 的存储底座之一)---- +# 是否启用 LMQ,启用后每个队列可承载大量轻量消息,默认 false;需要配合 Lite 使用时再打开 +enableLmq=false +# 是否启用 LMQ 配额控制,默认 false +enableLmqQuota=false + +# ---- Controller 模式(5.x 主从自动切换)---- +# 是否以 Controller 模式启动 Broker(自动选主,替代人工主从切换),默认 false +# 注意:开启后必须同时运行 controller 组件(namesrv 内嵌 controller 或独立 controller 服务),否则 Broker 选不出主节点 +enableControllerMode=false +# Controller 地址列表,多个地址用分号分隔;仅在 enableControllerMode=true 时生效 +controllerAddr= + +# ---- RocksDB 存储增强(5.x 默认存储后端,4.x 无)---- +# 事务消息是否使用 RocksDB 存储(半消息/op 消息),默认 false +transRocksDBEnable=false +# 启用 transRocksDBEnable 后,是否仍把原始半消息写入 CommitLog,默认 true +transWriteOriginTransHalfEnable=true + +# ---- 其它 5.x 才有的能力 ---- +# 是否开启 ConsumeQueue 扩展存储(存放消息 TAG 的哈希等),按需开启,默认 false +enableConsumeQueueExt=false diff --git a/deploy/rocketmq-5.5.0-cluster-1m2s/docker-compose.yml b/deploy/rocketmq-5.5.0-cluster-1m2s/docker-compose.yml index 3f5f835..aaf12ba 100644 --- a/deploy/rocketmq-5.5.0-cluster-1m2s/docker-compose.yml +++ b/deploy/rocketmq-5.5.0-cluster-1m2s/docker-compose.yml @@ -1,90 +1,80 @@ version: '3.8' -# 网桥 -> 方便相互通讯(172.21 段,避免与 rocketmq-4.9.7 的 172.20 冲突) +# 网桥 -> 方便相互通讯 networks: rocketmq: ipam: driver: default config: - - subnet: "172.21.0.0/24" + - subnet: "172.20.0.0/24" services: namesrv: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5namesrv - restart: unless-stopped + container_name: rmqnamesrv ports: - "9876:9876" - environment: - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M + volumes: + # 5.x 新增的 NameServer 配置(4.9.7 直接用默认配置,没有该文件) + - ./namesrv/conf/namesrv.conf:/home/rocketmq/rocketmq-5.5.0/conf/namesrv.conf networks: rocketmq: - ipv4_address: 172.21.0.80 - command: sh mqnamesrv + ipv4_address: 172.20.0.80 + command: sh mqnamesrv -c /home/rocketmq/rocketmq-5.5.0/conf/namesrv.conf broker1: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5broker1 - restart: unless-stopped + container_name: rmqbroker1 ports: - "10909:10909" - "10911:10911" - "10912:10912" environment: - NAMESRV_ADDR=rmqnamesrv:9876 - - ROCKETMQ_HOME=/home/rocketmq/rocketmq-5.5.0 - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M volumes: - ./broker-master/broker.conf:/home/rocketmq/rocketmq-5.5.0/conf/broker.conf - - ./broker-master/store:/home/rocketmq/rocketmq-5.5.0/store depends_on: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.81 + ipv4_address: 172.20.0.81 command: sh mqbroker -c /home/rocketmq/rocketmq-5.5.0/conf/broker.conf broker2: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5broker2 - restart: unless-stopped + container_name: rmqbroker2 ports: - "10809:10909" - "10811:10911" - "10812:10912" environment: - NAMESRV_ADDR=rmqnamesrv:9876 - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M volumes: - ./broker-slave1/broker.conf:/home/rocketmq/rocketmq-5.5.0/conf/broker.conf - - ./broker-slave1/store:/home/rocketmq/rocketmq-5.5.0/store depends_on: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.82 + ipv4_address: 172.20.0.82 command: sh mqbroker -c /home/rocketmq/rocketmq-5.5.0/conf/broker.conf broker3: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5broker3 - restart: unless-stopped + container_name: rmqbroker3 ports: - "10709:10909" - "10711:10911" - "10712:10912" environment: - NAMESRV_ADDR=rmqnamesrv:9876 - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M volumes: - ./broker-slave2/broker.conf:/home/rocketmq/rocketmq-5.5.0/conf/broker.conf - - ./broker-slave2/store:/home/rocketmq/rocketmq-5.5.0/store depends_on: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.83 + ipv4_address: 172.20.0.83 command: sh mqbroker -c /home/rocketmq/rocketmq-5.5.0/conf/broker.conf rmqdashboard: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apacherocketmq-rocketmq-dashboard-2.1.0 - container_name: rmq5dashboard + container_name: rocketmq-dashboard ports: - "8080:8082" restart: always @@ -92,6 +82,6 @@ services: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.84 + ipv4_address: 172.20.0.84 environment: - - JAVA_OPTS= -Xms256M -Xmx512M -Xmn128M -Drocketmq.namesrv.addr=rmqnamesrv:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false + - JAVA_OPTS= -Xms256M -Xms512M -Xmn128M -Drocketmq.namesrv.addr=rmqnamesrv:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false diff --git a/deploy/rocketmq-5.5.0-cluster-1m2s/namesrv/conf/namesrv.conf b/deploy/rocketmq-5.5.0-cluster-1m2s/namesrv/conf/namesrv.conf new file mode 100644 index 0000000..cbcf960 --- /dev/null +++ b/deploy/rocketmq-5.5.0-cluster-1m2s/namesrv/conf/namesrv.conf @@ -0,0 +1,36 @@ +# ===================== RocketMQ 5.5.0 NameServer 配置 ===================== +# 说明:4.9.7 的 mqnamesrv 用默认配置即可,没有独立配置文件;5.x 新增了 Lite Mode、LMQ、 +# Controller、RocksDB 等能力,其中与 NameServer 相关的新增项在此显式列出(均写成默认值,便于检索与调参)。 + +# kvConfig 持久化路径,默认 ~/namesrv/kvConfig.json;NameServer 在此保存 KV 配置、 +# 命名空间策略(NACOS 风格 namespace)等元数据,容器重建不保留,需要持久化时指向挂载目录 +kvConfigPath=/home/rocketmq/namesrv/kvConfig.json + +# 运行期配置存储路径(通过 updateNamesrvConfig 修改的配置落在这里),默认 ~/namesrv/namesrv.properties +configStorePath=/home/rocketmq/namesrv/namesrv.properties + +# 是否允许通过 updateNamesrvConfig 动态修改 NameServer 配置,被 configBlackList 列出的项除外 +# configBlackList 默认值:configBlackList;configStorePath;kvConfigPath +# configBlackList=configBlackList;configStorePath;kvConfigPath + +# ---- 5.x Lite Mode 依赖的路由能力(NameServer 侧无独立开关,依赖 Broker 上报)---- +# Lite Mode 的 Lite Topic 路由同样由 Broker 注册到 NameServer,NameServer 无需为 Lite 单独开配置; +# 若开启 Controller 模式(Broker 侧 enableControllerMode=true),需在 NameServer 内嵌 controller: +# enableControllerInNamesrv=true +# enableControllerInNamesrv=false + +# 是否在 NameServer 中等待 controller 可用后再启动(仅 enableControllerInNamesrv=true 时有意义),默认 false +# needWaitForService=false +# 等待 controller 的最长秒数,默认 45 +# waitSecondsForService=45 + +# ---- 其它 5.x 相关 ---- +# 是否开启顺序消息的 System Topic 支持(顺序消息路由相关),默认 false +# orderMessageEnable=false +# 是否把顺序消息 Topic 的路由信息回传给 Broker,默认 true +# returnOrderTopicConfigToBroker=true +# 允许从 Broker 注销时同步删除 NameServer 上不存在的 Topic,默认 false +# 注意:与 Broker 的 enableSingleTopicRegister 同时开启,否则可能误删路由 +# deleteTopicWithBrokerRegistration=false +# Broker 掉线扫描周期(毫秒),默认 5000 +# scanNotActiveBrokerInterval=5000 diff --git a/deploy/rocketmq-5.5.0-cluster-2m/broker-master1/broker.conf b/deploy/rocketmq-5.5.0-cluster-2m/broker-master1/broker.conf index 3d64d68..ea5f100 100644 --- a/deploy/rocketmq-5.5.0-cluster-2m/broker-master1/broker.conf +++ b/deploy/rocketmq-5.5.0-cluster-2m/broker-master1/broker.conf @@ -1,5 +1,5 @@ namesrvAddr=rmqnamesrv:9876 -brokerIP1=172.21.0.81 +brokerIP1=172.20.0.81 brokerName=rmqbroker1 brokerClusterName=rmqbroker brokerId=0 @@ -7,8 +7,8 @@ autoCreateTopicEnable=false autoCreateSubscriptionGroup=true rejectTransactionMessage=false fetchNamesrvAddrByAddressServer=false -storePathRootDir=/home/rocketmq/rocketmq-5.5.0/store -storePathCommitLog=/home/rocketmq/rocketmq-5.5.0/store/commitlog +storePathRootDir=/home/rocketmq/rocketmq-4.9.7/store +storePathCommitLog=/home/rocketmq/rocketmq-4.9.7/store/commitlog flushIntervalCommitLog=1000 flushCommitLogTimed=false deleteWhen=04 @@ -24,3 +24,60 @@ haMasterAddress= brokerRole=ASYNC_MASTER flushDiskType=ASYNC_FLUSH cleanFileForciblyEnable=true + +# ===================== RocketMQ 5.5.0 新特性(显式写出默认值,便于检索与调参) ===================== + +# ---- Lite Mode(RIP-83,5.5.0 唯一新增特性):面向 AI 场景的轻量级订阅模型 ---- +# 开关 Lite 事件分发,Lite Topic 的生命周期管理、订阅注册、指标上报都依赖它,默认 true +enableLiteEventMode=true +# Lite 事件分发扫描周期,单位毫秒;越小越实时,越大越省 CPU,默认 10000 +liteEventCheckInterval=10000 +# Lite Topic 过期检查周期,单位毫秒,默认 120000 +liteTtlCheckInterval=120000 +# Lite Topic 最短存活时间,单位毫秒,默认 900000(15 分钟),存活不足该时长的 Topic 不会被清理 +minLiteTTl=900000 +# Lite 订阅有效性检查周期,单位毫秒,默认 120000 +liteSubscriptionCheckInterval=120000 +# Lite 订阅检查超时时间,单位毫秒,默认 180000 +liteSubscriptionCheckTimeoutMills=180000 +# 单个 Broker 允许的 Lite 订阅数量上限,默认 100000 +maxLiteSubscriptionCount=100000 +# 是否打印 Lite POP 消费日志,排查 Lite 问题时临时置 true,默认 false +enableLitePopLog=false +# 单个 Lite 客户端连接允许挂载的最大事件数,默认 100 +maxClientEventCount=100 +# 全量分发延迟时间,单位毫秒,默认 10000,避免订阅建立瞬间的抖动 +liteEventFullDispatchDelayTime=10000 +# 通配订阅(wildcard group)的全量分发延迟时间,单位毫秒,默认 10000 +liteEventFullDispatchDelayTimeForWildcardGroup=10000 +# Lite 消费延迟指标:是否采集 storeTime(有额外开销),默认 false +liteLagLatencyCollectEnable=false +# 是否开启 Lite 消费延迟指标,默认 false +liteLagLatencyMetricsEnable=false +# 是否开启 Lite 堆积条数指标,默认 false +liteLagCountMetricsEnable=false +# Lite 延迟指标只统计 TopK,默认 50 +liteLagLatencyTopK=50 + +# ---- Light Message Queue(LMQ,5.x 轻量消息队列,Lite Mode 的存储底座之一)---- +# 是否启用 LMQ,启用后每个队列可承载大量轻量消息,默认 false;需要配合 Lite 使用时再打开 +enableLmq=false +# 是否启用 LMQ 配额控制,默认 false +enableLmqQuota=false + +# ---- Controller 模式(5.x 主从自动切换)---- +# 是否以 Controller 模式启动 Broker(自动选主,替代人工主从切换),默认 false +# 注意:开启后必须同时运行 controller 组件(namesrv 内嵌 controller 或独立 controller 服务),否则 Broker 选不出主节点 +enableControllerMode=false +# Controller 地址列表,多个地址用分号分隔;仅在 enableControllerMode=true 时生效 +controllerAddr= + +# ---- RocksDB 存储增强(5.x 默认存储后端,4.x 无)---- +# 事务消息是否使用 RocksDB 存储(半消息/op 消息),默认 false +transRocksDBEnable=false +# 启用 transRocksDBEnable 后,是否仍把原始半消息写入 CommitLog,默认 true +transWriteOriginTransHalfEnable=true + +# ---- 其它 5.x 才有的能力 ---- +# 是否开启 ConsumeQueue 扩展存储(存放消息 TAG 的哈希等),按需开启,默认 false +enableConsumeQueueExt=false diff --git a/deploy/rocketmq-5.5.0-cluster-2m/broker-master2/broker.conf b/deploy/rocketmq-5.5.0-cluster-2m/broker-master2/broker.conf index 2963ebd..bbdfe64 100644 --- a/deploy/rocketmq-5.5.0-cluster-2m/broker-master2/broker.conf +++ b/deploy/rocketmq-5.5.0-cluster-2m/broker-master2/broker.conf @@ -1,5 +1,5 @@ namesrvAddr=rmqnamesrv:9876 -brokerIP1=172.21.0.82 +brokerIP1=172.20.0.82 brokerName=rmqbroker2 brokerClusterName=rmqbroker brokerId=0 @@ -7,8 +7,8 @@ autoCreateTopicEnable=false autoCreateSubscriptionGroup=true rejectTransactionMessage=false fetchNamesrvAddrByAddressServer=false -storePathRootDir=/home/rocketmq/rocketmq-5.5.0/store -storePathCommitLog=/home/rocketmq/rocketmq-5.5.0/store/commitlog +storePathRootDir=/home/rocketmq/rocketmq-4.9.7/store +storePathCommitLog=/home/rocketmq/rocketmq-4.9.7/store/commitlog flushIntervalCommitLog=1000 flushCommitLogTimed=false deleteWhen=04 @@ -24,3 +24,60 @@ haMasterAddress= brokerRole=ASYNC_MASTER flushDiskType=ASYNC_FLUSH cleanFileForciblyEnable=true + +# ===================== RocketMQ 5.5.0 新特性(显式写出默认值,便于检索与调参) ===================== + +# ---- Lite Mode(RIP-83,5.5.0 唯一新增特性):面向 AI 场景的轻量级订阅模型 ---- +# 开关 Lite 事件分发,Lite Topic 的生命周期管理、订阅注册、指标上报都依赖它,默认 true +enableLiteEventMode=true +# Lite 事件分发扫描周期,单位毫秒;越小越实时,越大越省 CPU,默认 10000 +liteEventCheckInterval=10000 +# Lite Topic 过期检查周期,单位毫秒,默认 120000 +liteTtlCheckInterval=120000 +# Lite Topic 最短存活时间,单位毫秒,默认 900000(15 分钟),存活不足该时长的 Topic 不会被清理 +minLiteTTl=900000 +# Lite 订阅有效性检查周期,单位毫秒,默认 120000 +liteSubscriptionCheckInterval=120000 +# Lite 订阅检查超时时间,单位毫秒,默认 180000 +liteSubscriptionCheckTimeoutMills=180000 +# 单个 Broker 允许的 Lite 订阅数量上限,默认 100000 +maxLiteSubscriptionCount=100000 +# 是否打印 Lite POP 消费日志,排查 Lite 问题时临时置 true,默认 false +enableLitePopLog=false +# 单个 Lite 客户端连接允许挂载的最大事件数,默认 100 +maxClientEventCount=100 +# 全量分发延迟时间,单位毫秒,默认 10000,避免订阅建立瞬间的抖动 +liteEventFullDispatchDelayTime=10000 +# 通配订阅(wildcard group)的全量分发延迟时间,单位毫秒,默认 10000 +liteEventFullDispatchDelayTimeForWildcardGroup=10000 +# Lite 消费延迟指标:是否采集 storeTime(有额外开销),默认 false +liteLagLatencyCollectEnable=false +# 是否开启 Lite 消费延迟指标,默认 false +liteLagLatencyMetricsEnable=false +# 是否开启 Lite 堆积条数指标,默认 false +liteLagCountMetricsEnable=false +# Lite 延迟指标只统计 TopK,默认 50 +liteLagLatencyTopK=50 + +# ---- Light Message Queue(LMQ,5.x 轻量消息队列,Lite Mode 的存储底座之一)---- +# 是否启用 LMQ,启用后每个队列可承载大量轻量消息,默认 false;需要配合 Lite 使用时再打开 +enableLmq=false +# 是否启用 LMQ 配额控制,默认 false +enableLmqQuota=false + +# ---- Controller 模式(5.x 主从自动切换)---- +# 是否以 Controller 模式启动 Broker(自动选主,替代人工主从切换),默认 false +# 注意:开启后必须同时运行 controller 组件(namesrv 内嵌 controller 或独立 controller 服务),否则 Broker 选不出主节点 +enableControllerMode=false +# Controller 地址列表,多个地址用分号分隔;仅在 enableControllerMode=true 时生效 +controllerAddr= + +# ---- RocksDB 存储增强(5.x 默认存储后端,4.x 无)---- +# 事务消息是否使用 RocksDB 存储(半消息/op 消息),默认 false +transRocksDBEnable=false +# 启用 transRocksDBEnable 后,是否仍把原始半消息写入 CommitLog,默认 true +transWriteOriginTransHalfEnable=true + +# ---- 其它 5.x 才有的能力 ---- +# 是否开启 ConsumeQueue 扩展存储(存放消息 TAG 的哈希等),按需开启,默认 false +enableConsumeQueueExt=false diff --git a/deploy/rocketmq-5.5.0-cluster-2m/docker-compose.yml b/deploy/rocketmq-5.5.0-cluster-2m/docker-compose.yml index 81e01c9..ccbb771 100644 --- a/deploy/rocketmq-5.5.0-cluster-2m/docker-compose.yml +++ b/deploy/rocketmq-5.5.0-cluster-2m/docker-compose.yml @@ -1,70 +1,63 @@ version: '3.8' -# 网桥 -> 方便相互通讯(172.21 段,避免与 rocketmq-4.9.7 的 172.20 冲突) +# 网桥 -> 方便相互通讯 networks: rocketmq: ipam: driver: default config: - - subnet: "172.21.0.0/24" + - subnet: "172.20.0.0/24" services: namesrv: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5namesrv - restart: unless-stopped + container_name: rmqnamesrv ports: - "9876:9876" - environment: - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M + volumes: + # 5.x 新增的 NameServer 配置(4.9.7 直接用默认配置,没有该文件) + - ./namesrv/conf/namesrv.conf:/home/rocketmq/rocketmq-5.5.0/conf/namesrv.conf networks: rocketmq: - ipv4_address: 172.21.0.80 - command: sh mqnamesrv + ipv4_address: 172.20.0.80 + command: sh mqnamesrv -c /home/rocketmq/rocketmq-5.5.0/conf/namesrv.conf broker1: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5broker1 - restart: unless-stopped + container_name: rmqbroker1 ports: - "10909:10909" - "10911:10911" - "10912:10912" environment: - NAMESRV_ADDR=rmqnamesrv:9876 - - ROCKETMQ_HOME=/home/rocketmq/rocketmq-5.5.0 - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M volumes: - ./broker-master1/broker.conf:/home/rocketmq/rocketmq-5.5.0/conf/broker.conf - - ./broker-master1/store:/home/rocketmq/rocketmq-5.5.0/store depends_on: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.81 + ipv4_address: 172.20.0.81 command: sh mqbroker -c /home/rocketmq/rocketmq-5.5.0/conf/broker.conf broker2: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5broker2 - restart: unless-stopped + container_name: rmqbroker2 ports: - "10809:10909" - "10811:10911" - "10812:10912" environment: - NAMESRV_ADDR=rmqnamesrv:9876 - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M volumes: - ./broker-master2/broker.conf:/home/rocketmq/rocketmq-5.5.0/conf/broker.conf - - ./broker-master2/store:/home/rocketmq/rocketmq-5.5.0/store depends_on: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.82 + ipv4_address: 172.20.0.82 command: sh mqbroker -c /home/rocketmq/rocketmq-5.5.0/conf/broker.conf rmqdashboard: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apacherocketmq-rocketmq-dashboard-2.1.0 - container_name: rmq5dashboard + container_name: rocketmq-dashboard ports: - "8080:8082" restart: always @@ -72,6 +65,6 @@ services: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.83 + ipv4_address: 172.20.0.83 environment: - - JAVA_OPTS= -Xms256M -Xmx512M -Xmn128M -Drocketmq.namesrv.addr=rmqnamesrv:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false + - JAVA_OPTS= -Xms256M -Xms512M -Xmn128M -Drocketmq.namesrv.addr=rmqnamesrv:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false diff --git a/deploy/rocketmq-5.5.0-cluster-2m/namesrv/conf/namesrv.conf b/deploy/rocketmq-5.5.0-cluster-2m/namesrv/conf/namesrv.conf new file mode 100644 index 0000000..cbcf960 --- /dev/null +++ b/deploy/rocketmq-5.5.0-cluster-2m/namesrv/conf/namesrv.conf @@ -0,0 +1,36 @@ +# ===================== RocketMQ 5.5.0 NameServer 配置 ===================== +# 说明:4.9.7 的 mqnamesrv 用默认配置即可,没有独立配置文件;5.x 新增了 Lite Mode、LMQ、 +# Controller、RocksDB 等能力,其中与 NameServer 相关的新增项在此显式列出(均写成默认值,便于检索与调参)。 + +# kvConfig 持久化路径,默认 ~/namesrv/kvConfig.json;NameServer 在此保存 KV 配置、 +# 命名空间策略(NACOS 风格 namespace)等元数据,容器重建不保留,需要持久化时指向挂载目录 +kvConfigPath=/home/rocketmq/namesrv/kvConfig.json + +# 运行期配置存储路径(通过 updateNamesrvConfig 修改的配置落在这里),默认 ~/namesrv/namesrv.properties +configStorePath=/home/rocketmq/namesrv/namesrv.properties + +# 是否允许通过 updateNamesrvConfig 动态修改 NameServer 配置,被 configBlackList 列出的项除外 +# configBlackList 默认值:configBlackList;configStorePath;kvConfigPath +# configBlackList=configBlackList;configStorePath;kvConfigPath + +# ---- 5.x Lite Mode 依赖的路由能力(NameServer 侧无独立开关,依赖 Broker 上报)---- +# Lite Mode 的 Lite Topic 路由同样由 Broker 注册到 NameServer,NameServer 无需为 Lite 单独开配置; +# 若开启 Controller 模式(Broker 侧 enableControllerMode=true),需在 NameServer 内嵌 controller: +# enableControllerInNamesrv=true +# enableControllerInNamesrv=false + +# 是否在 NameServer 中等待 controller 可用后再启动(仅 enableControllerInNamesrv=true 时有意义),默认 false +# needWaitForService=false +# 等待 controller 的最长秒数,默认 45 +# waitSecondsForService=45 + +# ---- 其它 5.x 相关 ---- +# 是否开启顺序消息的 System Topic 支持(顺序消息路由相关),默认 false +# orderMessageEnable=false +# 是否把顺序消息 Topic 的路由信息回传给 Broker,默认 true +# returnOrderTopicConfigToBroker=true +# 允许从 Broker 注销时同步删除 NameServer 上不存在的 Topic,默认 false +# 注意:与 Broker 的 enableSingleTopicRegister 同时开启,否则可能误删路由 +# deleteTopicWithBrokerRegistration=false +# Broker 掉线扫描周期(毫秒),默认 5000 +# scanNotActiveBrokerInterval=5000 diff --git a/deploy/rocketmq-5.5.0-standalone/docker-compose.yml b/deploy/rocketmq-5.5.0-standalone/docker-compose.yml index 5f7c1b4..7e60e5f 100644 --- a/deploy/rocketmq-5.5.0-standalone/docker-compose.yml +++ b/deploy/rocketmq-5.5.0-standalone/docker-compose.yml @@ -1,50 +1,46 @@ version: '3.8' -# 网桥 -> 方便相互通讯(172.21 段,避免与 rocketmq-4.9.7 的 172.20 冲突) +# 网桥 -> 方便相互通讯 networks: rocketmq: ipam: driver: default config: - - subnet: "172.21.0.0/24" + - subnet: "172.20.0.0/24" services: namesrv: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5namesrv - restart: unless-stopped + container_name: rmqnamesrv ports: - "9876:9876" - environment: - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M + volumes: + # 5.x 新增的 NameServer 配置(4.9.7 直接用默认配置,没有该文件) + - ./namesrv/conf/namesrv.conf:/home/rocketmq/rocketmq-5.5.0/conf/namesrv.conf networks: rocketmq: - ipv4_address: 172.21.0.80 - command: sh mqnamesrv + ipv4_address: 172.20.0.80 + command: sh mqnamesrv -c /home/rocketmq/rocketmq-5.5.0/conf/namesrv.conf broker: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apache-rocketmq-5.5.0 - container_name: rmq5broker - restart: unless-stopped + container_name: rmqbroker ports: - "10909:10909" - "10911:10911" - "10912:10912" environment: - NAMESRV_ADDR=rmqnamesrv:9876 - - ROCKETMQ_HOME=/home/rocketmq/rocketmq-5.5.0 - - JAVA_OPTIONS=-Xms512M -Xmx512M -Xmn256M volumes: - ./master/broker.conf:/home/rocketmq/rocketmq-5.5.0/conf/broker.conf - - ./master/store:/home/rocketmq/rocketmq-5.5.0/store depends_on: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.81 + ipv4_address: 172.20.0.81 command: sh mqbroker -c /home/rocketmq/rocketmq-5.5.0/conf/broker.conf rmqdashboard: image: registry.cn-shanghai.aliyuncs.com/odboy/thirdrepo:apacherocketmq-rocketmq-dashboard-2.1.0 - container_name: rmq5dashboard + container_name: rocketmq-dashboard ports: - "8080:8082" restart: always @@ -52,6 +48,6 @@ services: - namesrv networks: rocketmq: - ipv4_address: 172.21.0.82 + ipv4_address: 172.20.0.82 environment: - - JAVA_OPTS= -Xms256M -Xmx512M -Xmn128M -Drocketmq.namesrv.addr=rmqnamesrv:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false + - JAVA_OPTS= -Xms256M -Xms512M -Xmn128M -Drocketmq.namesrv.addr=rmqnamesrv:9876 -Dcom.rocketmq.sendMessageWithVIPChannel=false diff --git a/deploy/rocketmq-5.5.0-standalone/master/broker.conf b/deploy/rocketmq-5.5.0-standalone/master/broker.conf index db6d98a..6fd4f2c 100644 --- a/deploy/rocketmq-5.5.0-standalone/master/broker.conf +++ b/deploy/rocketmq-5.5.0-standalone/master/broker.conf @@ -1,5 +1,5 @@ namesrvAddr=rmqnamesrv:9876 -brokerIP1=172.21.0.81 +brokerIP1=172.20.0.81 brokerName=rmqbroker brokerClusterName=rmqbroker brokerId=0 @@ -7,8 +7,8 @@ autoCreateTopicEnable=false autoCreateSubscriptionGroup=true rejectTransactionMessage=false fetchNamesrvAddrByAddressServer=false -storePathRootDir=/home/rocketmq/rocketmq-5.5.0/store -storePathCommitLog=/home/rocketmq/rocketmq-5.5.0/store/commitlog +storePathRootDir=/home/rocketmq/rocketmq-4.9.7/store +storePathCommitLog=/home/rocketmq/rocketmq-4.9.7/store/commitlog flushIntervalCommitLog=1000 flushCommitLogTimed=false deleteWhen=04 @@ -24,3 +24,60 @@ haMasterAddress= brokerRole=ASYNC_MASTER flushDiskType=ASYNC_FLUSH cleanFileForciblyEnable=true + +# ===================== RocketMQ 5.5.0 新特性(显式写出默认值,便于检索与调参) ===================== + +# ---- Lite Mode(RIP-83,5.5.0 唯一新增特性):面向 AI 场景的轻量级订阅模型 ---- +# 开关 Lite 事件分发,Lite Topic 的生命周期管理、订阅注册、指标上报都依赖它,默认 true +enableLiteEventMode=true +# Lite 事件分发扫描周期,单位毫秒;越小越实时,越大越省 CPU,默认 10000 +liteEventCheckInterval=10000 +# Lite Topic 过期检查周期,单位毫秒,默认 120000 +liteTtlCheckInterval=120000 +# Lite Topic 最短存活时间,单位毫秒,默认 900000(15 分钟),存活不足该时长的 Topic 不会被清理 +minLiteTTl=900000 +# Lite 订阅有效性检查周期,单位毫秒,默认 120000 +liteSubscriptionCheckInterval=120000 +# Lite 订阅检查超时时间,单位毫秒,默认 180000 +liteSubscriptionCheckTimeoutMills=180000 +# 单个 Broker 允许的 Lite 订阅数量上限,默认 100000 +maxLiteSubscriptionCount=100000 +# 是否打印 Lite POP 消费日志,排查 Lite 问题时临时置 true,默认 false +enableLitePopLog=false +# 单个 Lite 客户端连接允许挂载的最大事件数,默认 100 +maxClientEventCount=100 +# 全量分发延迟时间,单位毫秒,默认 10000,避免订阅建立瞬间的抖动 +liteEventFullDispatchDelayTime=10000 +# 通配订阅(wildcard group)的全量分发延迟时间,单位毫秒,默认 10000 +liteEventFullDispatchDelayTimeForWildcardGroup=10000 +# Lite 消费延迟指标:是否采集 storeTime(有额外开销),默认 false +liteLagLatencyCollectEnable=false +# 是否开启 Lite 消费延迟指标,默认 false +liteLagLatencyMetricsEnable=false +# 是否开启 Lite 堆积条数指标,默认 false +liteLagCountMetricsEnable=false +# Lite 延迟指标只统计 TopK,默认 50 +liteLagLatencyTopK=50 + +# ---- Light Message Queue(LMQ,5.x 轻量消息队列,Lite Mode 的存储底座之一)---- +# 是否启用 LMQ,启用后每个队列可承载大量轻量消息,默认 false;需要配合 Lite 使用时再打开 +enableLmq=false +# 是否启用 LMQ 配额控制,默认 false +enableLmqQuota=false + +# ---- Controller 模式(5.x 主从自动切换)---- +# 是否以 Controller 模式启动 Broker(自动选主,替代人工主从切换),默认 false +# 注意:开启后必须同时运行 controller 组件(namesrv 内嵌 controller 或独立 controller 服务),否则 Broker 选不出主节点 +enableControllerMode=false +# Controller 地址列表,多个地址用分号分隔;仅在 enableControllerMode=true 时生效 +controllerAddr= + +# ---- RocksDB 存储增强(5.x 默认存储后端,4.x 无)---- +# 事务消息是否使用 RocksDB 存储(半消息/op 消息),默认 false +transRocksDBEnable=false +# 启用 transRocksDBEnable 后,是否仍把原始半消息写入 CommitLog,默认 true +transWriteOriginTransHalfEnable=true + +# ---- 其它 5.x 才有的能力 ---- +# 是否开启 ConsumeQueue 扩展存储(存放消息 TAG 的哈希等),按需开启,默认 false +enableConsumeQueueExt=false diff --git a/deploy/rocketmq-5.5.0-standalone/namesrv/conf/namesrv.conf b/deploy/rocketmq-5.5.0-standalone/namesrv/conf/namesrv.conf new file mode 100644 index 0000000..cbcf960 --- /dev/null +++ b/deploy/rocketmq-5.5.0-standalone/namesrv/conf/namesrv.conf @@ -0,0 +1,36 @@ +# ===================== RocketMQ 5.5.0 NameServer 配置 ===================== +# 说明:4.9.7 的 mqnamesrv 用默认配置即可,没有独立配置文件;5.x 新增了 Lite Mode、LMQ、 +# Controller、RocksDB 等能力,其中与 NameServer 相关的新增项在此显式列出(均写成默认值,便于检索与调参)。 + +# kvConfig 持久化路径,默认 ~/namesrv/kvConfig.json;NameServer 在此保存 KV 配置、 +# 命名空间策略(NACOS 风格 namespace)等元数据,容器重建不保留,需要持久化时指向挂载目录 +kvConfigPath=/home/rocketmq/namesrv/kvConfig.json + +# 运行期配置存储路径(通过 updateNamesrvConfig 修改的配置落在这里),默认 ~/namesrv/namesrv.properties +configStorePath=/home/rocketmq/namesrv/namesrv.properties + +# 是否允许通过 updateNamesrvConfig 动态修改 NameServer 配置,被 configBlackList 列出的项除外 +# configBlackList 默认值:configBlackList;configStorePath;kvConfigPath +# configBlackList=configBlackList;configStorePath;kvConfigPath + +# ---- 5.x Lite Mode 依赖的路由能力(NameServer 侧无独立开关,依赖 Broker 上报)---- +# Lite Mode 的 Lite Topic 路由同样由 Broker 注册到 NameServer,NameServer 无需为 Lite 单独开配置; +# 若开启 Controller 模式(Broker 侧 enableControllerMode=true),需在 NameServer 内嵌 controller: +# enableControllerInNamesrv=true +# enableControllerInNamesrv=false + +# 是否在 NameServer 中等待 controller 可用后再启动(仅 enableControllerInNamesrv=true 时有意义),默认 false +# needWaitForService=false +# 等待 controller 的最长秒数,默认 45 +# waitSecondsForService=45 + +# ---- 其它 5.x 相关 ---- +# 是否开启顺序消息的 System Topic 支持(顺序消息路由相关),默认 false +# orderMessageEnable=false +# 是否把顺序消息 Topic 的路由信息回传给 Broker,默认 true +# returnOrderTopicConfigToBroker=true +# 允许从 Broker 注销时同步删除 NameServer 上不存在的 Topic,默认 false +# 注意:与 Broker 的 enableSingleTopicRegister 同时开启,否则可能误删路由 +# deleteTopicWithBrokerRegistration=false +# Broker 掉线扫描周期(毫秒),默认 5000 +# scanNotActiveBrokerInterval=5000