bin>mqbroker.cmd -c ../conf/2m-2s-async/broker-b-s.properties 错误信息:Lock failed,MQ already started

RocketMQ启动异常解决

最新推荐文章于 2025-01-11 16:12:54 发布

原创最新推荐文章于 2025-01-11 16:12:54 发布 · 850 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#spring boot

消息中间件专栏收录该内容

1 篇文章

订阅专栏

本文详细解析了在启动RocketMQ集群时遇到的Lock failed, MQ already started异常，指出该问题是由于master和slave节点共用了同一storePath路径。通过调整配置文件中的storePathRootDir和storePathCommitLog属性，为每个broker指定独立的存储路径，成功解决了启动冲突问题。

E:\home\rocketmq-all-4.6.0-bin-release\bin>mqbroker.cmd -c ../conf/2m-2s-async/broker-b-s.properties
java.lang.RuntimeException: Lock failed,MQ already started
        at org.apache.rocketmq.store.DefaultMessageStore.start(DefaultMessageStore.java:222)
        at org.apache.rocketmq.broker.BrokerController.start(BrokerController.java:853)
        at org.apache.rocketmq.broker.BrokerStartup.start(BrokerStartup.java:64)
        at org.apache.rocketmq.broker.BrokerStartup.main(BrokerStartup.java:58)

原因:在集群中master和slave共用一个storePath造成的

解决方案:我们要启动的每一个broker要指定不一样的storePath 路径就行，也就是在我们的配置文件中修改即可,如更改配置文件storePathRootDir和storePathCommitLog属性路径

broker-a.properties

storePathRootDir=E:/home/rocketmq-all-4.6.0-bin-release/data/broker-a/store
storePathCommitLog=E:/home/rocketmq-all-4.6.0-bin-release/data/broker-a/store/commitlog

broker-a-s.properties

storePathRootDir=E:/home/rocketmq-all-4.6.0-bin-release/data/broker-a-s/store
storePathCommitLog=E:/home/rocketmq-all-4.6.0-bin-release/data/broker-a-s/store/commitlog

broker-b.properties和broker-b-s.properties同理