首页 文章

设置RocketMQ集群:slave不可见且不复制

提问于
浏览
0

我正在尝试 Build 一个RocketMQ集群,其中包含一个名称服务器,一个主服务器和两个从服务器 . 但是,我遇到了一些问题 .

我正在运行的版本是从github/rocketmq-all-4.1.0-incubating.zip下载的 .

代理使用 mqbroker -c broker.conf 运行,其中broker.conf对主服务器和从服务器不同 . 对于大师我有:

listenPort=10911
brokerName=mybroker
brokerClusterName=mybrokercluster
brokerId=0
deleteWhen=04
fileReservedTime=48
brokerRole=SYNC_MASTER
flushDiskType=ASYNC_FLUSH

而对于奴隶:

listenPort=10911
brokerName=mybroker
brokerClusterName=mybrokercluster
brokerId=1
deleteWhen=04
fileReservedTime=48
brokerRole=SLAVE
flushDiskType=ASYNC_FLUSH

第二个奴隶有 brokerId=2 . 经纪人开始很好,一些奴隶的日志部分:

2017-10-02 20:31:35 INFO main - brokerRole=ASYNC_MASTER
2017-10-02 20:31:35 INFO main - flushDiskType=ASYNC_FLUSH
(...)
2017-10-02 20:31:35 INFO main - Replace, key: brokerId, value: 0 -> 1
2017-10-02 20:31:35 INFO main - Replace, key: brokerRole, value:
ASYNC_MASTER -> SLAVE
(...)
2017-10-02 20:31:37 INFO main - Set user specified name server address:
172.22.1.38:9876
2017-10-02 20:31:37 INFO ShutdownHook - Shutdown hook was invoked, 1
2017-10-02 20:31:37 INFO ShutdownHook - shutdown thread
PullRequestHoldService interrupt false
2017-10-02 20:31:37 INFO ShutdownHook - join thread PullRequestHoldService
eclipse time(ms) 0 90000
2017-10-02 20:31:37 WARN ShutdownHook - unregisterBroker Exception,
172.22.1.38:9876
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to
<172.22.1.38:9876> failed
at
org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:359)
~[rocketmq-remoting-4.1.0-incubating.jar:4.1.0-incubating]
at
org.apache.rocketmq.broker.out.BrokerOuterAPI.unregisterBroker(BrokerOuterAPI.java:221)
~[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at
org.apache.rocketmq.broker.out.BrokerOuterAPI.unregisterBrokerAll(BrokerOuterAPI.java:198)
~[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at
org.apache.rocketmq.broker.BrokerController.unregisterBrokerAll(BrokerController.java:623)
[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at
org.apache.rocketmq.broker.BrokerController.shutdown(BrokerController.java:589)
[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at org.apache.rocketmq.broker.BrokerStartup$1.run(BrokerStartup.java:218)
[rocketmq-broker-4.1.0-incubating.jar:4.1.0-incubating]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_141]
2017-10-02 20:31:37 INFO ShutdownHook - Shutdown hook over, consuming total
time(ms): 25
2017-10-02 20:31:45 INFO BrokerControllerScheduledThread1 - dispatch behind
commit log 0 bytes
2017-10-02 20:31:45 INFO BrokerControllerScheduledThread1 - Slave fall
behind master: 0 bytes
2017-10-02 20:31:45 INFO BrokerControllerScheduledThread1 - register broker
to name server 172.22.1.38:9876 OK
2017-10-02 20:32:15 INFO BrokerControllerScheduledThread1 - register broker
to name server 172.22.1.38:9876 OK

因为我怀疑代理正在尝试连接到最初没有运行的名称服务器,所以它重试并最终成功?

但是,稍后在尝试clusterList时,我只看到列出的一个代理,它恰好是一个从属( 172.22.1.17 )并且在配置中有 brokerId=2 (虽然这里列为0):

$ ./mqadmin clusterList -n 172.22.1.38:9876
#Cluster Name     #Broker Name            #BID  #Addr
 #Version                #InTPS(LOAD)       #OutTPS(LOAD) #PCWait(ms) #Hour
#SPACE
mybrokercluster     mybroker                  0     172.22.1.17:10911
 V4_1_0_SNAPSHOT          0.00(0,0ms)         0.00(0,0ms)          0
418597.80 -1.0000

而且,当向主人发送消息时,我得到 SLAVE_NOT_AVAILABLE .

这是为什么?经纪人配置得当吗?如果是这样,那么 clusterList 报错了吗?

1 回答

  • 0

    你应该改变slave端口,你知道10911已经被anthoer进程(主节点)使用,slave应该使用不同的tcp端口(例如 . 10921/10931等)

    提示:我的集群部署在一台机器上,所以我改变了tcp端口并启动成功,如果你在不同机器上进行主从部署并且启动失败,你应该访问rocketmq错误日志获取更多信息 .

    注意:一个拥有多个slave的master,brokerId应该是不同的

相关问题