请稍等 ...
×

采纳答案成功！

向帮助你的同学说点啥吧！感谢那些助人为乐的人

故障演练时，master 关闭，Consumer 无法从 Slave 消费

老师您好，能帮忙看下吗？
我用的两台腾讯云服务器（CentOS 7.x），

经测试，我 2 台服务器，作为单主时，都能正常使用。
配置为主从时，rocketmq-console 可以正常看到主从节点：
图片描述
但是，
1、Producer 发1条消息后，
Producer 控制台：
图片描述
2、关闭 Master ，再启动 Consumer ，无法消费。不知道问题出在哪？？？
Consumer 控制台：
图片描述
3、Master 重新启动后 Consumer 可以消费
Consumer 控制台：
图片描述

=> 似乎主从关系没有配置好

找了一晚上不知道问题出在哪，求帮助！！！
这个弄不好，后面的双主双从也没法弄，好纠结… …

下面是我的 broker 主从配置：

broker-a.properties 示例：
---------------------------------------demo begin

#所属集群名字（例如：双主双从中的所有 broker 节点，都属于同一 broker 集群）
brokerClusterName=rocketmq-cluster

#broker 名字。注意：主从节点 brokerName 一致。
brokerName=broker-a

#0 表示 Master，>0 表示 Slave
brokerId=0

#【注意】：若使用云服务器，则很可能存在多网卡（特点：有内网IP和外网IP），必须指明此参数
#broker 地址，值为公网 IP 地址
brokerIP1=148.70.109.178
brokerIP2=148.70.109.178

#nameServer 地址，分号分割
#【注意】：nameserver 地址必须先在 /etc/hosts 文件中进行了 IP 配置
namesrvAddr=rocketmq-nameserver1:9876;rocketmq-nameserver2:9876

#在发送消息时，自动创建服务器不存在的 topic，默认创建的队列数
defaultTopicQueueNums=4

#是否允许 Broker 自动创建 Topic，建议线下开启，线上关闭
autoCreateTopicEnable=true

#是否允许 Broker 自动创建订阅组，建议线下开启，线上关闭
autoCreateSubscriptionGroup=true

#Broker 对外服务的监听端口
listenPort=10911

#删除文件时间点，默认凌晨 4 点
deleteWhen=04

#文件保留时间，单位：小时。默认 48 小时。
fileReservedTime=120

#commitLog 每个文件的大小默认 1G
mapedFileSizeCommitLog=1073741824

#ConsumeQueue 每个文件默认存 30W 条，根据业务情况调整
mapedFileSizeConsumeQueue=300000

#destroyMapedFileIntervalForcibly=120000
#redeleteHangedFileInterval=120000

#检测物理文件磁盘空间
diskMaxUsedSpaceRatio=88

#存储路径
#【注意】：该目录需要提前创建
storePathRootDir=/usr/local/rocketmq/store

#commitLog 存储路径
#【注意】：该目录需要提前创建
storePathCommitLog=/usr/local/rocketmq/store/commitlog

#消费队列存储路径存储路径
#【注意】：该目录需要提前创建
storePathConsumeQueue=/usr/local/rocketmq/store/consumequeue

#消息索引存储路径
#【注意】：该目录需要提前创建
storePathIndex=/usr/local/rocketmq/store/index

#checkpoint 文件存储路径
#【提示】：该目录会自动生成
storeCheckpoint=/usr/local/rocketmq/store/checkpoint

#abort 文件存储路径
#【提示】：该目录会自动生成
abortFile=/usr/local/rocketmq/store/abort

#限制的消息大小
maxMessageSize=65536

#flushCommitLogLeastPages=4
#flushConsumeQueueLeastPages=2
#flushCommitLogThoroughInterval=10000
#flushConsumeQueueThoroughInterval=60000

#Broker 的角色
#- ASYNC_MASTER 异步复制 Master
#- SYNC_MASTER 同步双写 Master
#- SLAVE
brokerRole=ASYNC_MASTER

#刷盘方式
#- ASYNC_FLUSH 异步刷盘
#- SYNC_FLUSH 同步刷盘
flushDiskType=ASYNC_FLUSH

#checkTransactionMessageEnable=false

#发消息线程池数量
#sendMessageThreadPoolNums=128

#拉消息线程池数量
#pullMessageThreadPoolNums=128

---------------------------------------demo end
broker-a-s.properties 示例：
---------------------------------------demo begin

#所属集群名字（例如：双主双从中的所有 broker 节点，都属于同一 broker 集群）
brokerClusterName=rocketmq-cluster

#broker 名字。注意：主从节点 brokerName 一致。
brokerName=broker-a

#0 表示 Master，>0 表示 Slave
brokerId=1

#【注意】：若使用云服务器，则很可能存在多网卡（特点：有内网IP和外网IP），必须指明此参数
#broker 地址，值为公网 IP 地址
brokerIP1=132.232.13.10

#nameServer 地址，分号分割
#【注意】：nameserver 地址必须先在 /etc/hosts 文件中进行了 IP 配置
namesrvAddr=rocketmq-nameserver1:9876;rocketmq-nameserver2:9876

#在发送消息时，自动创建服务器不存在的 topic，默认创建的队列数
defaultTopicQueueNums=4

#是否允许 Broker 自动创建 Topic，建议线下开启，线上关闭
autoCreateTopicEnable=true

#是否允许 Broker 自动创建订阅组，建议线下开启，线上关闭
autoCreateSubscriptionGroup=true

#Broker 对外服务的监听端口
listenPort=10911

#删除文件时间点，默认凌晨 4 点
deleteWhen=04

#文件保留时间，单位：小时。默认 48 小时。
fileReservedTime=120

#commitLog 每个文件的大小默认 1G
mapedFileSizeCommitLog=1073741824

#ConsumeQueue 每个文件默认存 30W 条，根据业务情况调整
mapedFileSizeConsumeQueue=300000

#destroyMapedFileIntervalForcibly=120000
#redeleteHangedFileInterval=120000

#检测物理文件磁盘空间
diskMaxUsedSpaceRatio=88

#存储路径
#【注意】：该目录需要提前创建
storePathRootDir=/usr/local/rocketmq/store

#commitLog 存储路径
#【注意】：该目录需要提前创建
storePathCommitLog=/usr/local/rocketmq/store/commitlog

#消费队列存储路径存储路径
#【注意】：该目录需要提前创建
storePathConsumeQueue=/usr/local/rocketmq/store/consumequeue

#消息索引存储路径
#【注意】：该目录需要提前创建
storePathIndex=/usr/local/rocketmq/store/index

#checkpoint 文件存储路径
#【提示】：该目录会自动生成
storeCheckpoint=/usr/local/rocketmq/store/checkpoint

#abort 文件存储路径
#【提示】：该目录会自动生成
abortFile=/usr/local/rocketmq/store/abort

#限制的消息大小
maxMessageSize=65536

#flushCommitLogLeastPages=4
#flushConsumeQueueLeastPages=2
#flushCommitLogThoroughInterval=10000
#flushConsumeQueueThoroughInterval=60000

#Broker 的角色
#- ASYNC_MASTER 异步复制 Master
#- SYNC_MASTER 同步双写 Master
#- SLAVE
brokerRole=SLAVE

#刷盘方式
#- ASYNC_FLUSH 异步刷盘
#- SYNC_FLUSH 同步刷盘
flushDiskType=ASYNC_FLUSH

#checkTransactionMessageEnable=false

#发消息线程池数量
#sendMessageThreadPoolNums=128

#拉消息线程池数量
#pullMessageThreadPoolNums=128

---------------------------------------demo end

hosts：

[root@VM_0_15_centos bin]# cat /etc/hosts
127.0.0.1 VM_0_15_centos VM_0_15_centos
127.0.0.1 localhost.localdomain localhost
127.0.0.1 localhost4.localdomain4 localhost4

::1 VM_0_15_centos VM_0_15_centos
::1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

148.70.109.178  rocketmq-nameserver1
148.70.109.178  rocketmq-master1
132.232.13.10  rocketmq-nameserver2
132.232.13.10  rocketmq-master1-slave
梨多情 2020-02-24 01:16:20
源自：3-5  主从集群模式下的高可用机制故障演练
1679
收起

正在回答 回答被采纳积分+3

5回答

提问者 梨多情 2020-02-25 16:08:10

解决了，但是什么原因没搞懂？？？
我把 store 相关目录清空了，重试一次就 ok 了。

我昨天看过一篇文章，说是在这种场景下，consumer 抛异常也会出现类似死循环的情况，但是我用的是监听，并未抛异常。

不过这篇文章写的挺好的，非常具有参考意义，可以看下：

单Broker集群，RocketMQ宕机时消费失败会有什么问题 - 云+社区 - 腾讯云  https://cloud.tencent.com/developer/news/158048

0 回复 有任何疑惑可以回复我~
收起回答
取消 回复
阿神 2020-02-25 13:28:25

在群里解决~

0 回复 有任何疑惑可以回复我~
收起回答
取消 回复
提问者 梨多情 2020-02-24 17:03:40

因此处字数受限，Slave 日志后续如下：（下面是死循环的警告日志，每秒刷几十次）

2020-02-24 16:32:40 INFO brokerOutApi_thread_4 - register broker[1]to name server rocketmq-nameserver2:9876 OK

2020-02-24 16:33:04 INFO HeartbeatThread_3 - new consumer connected, group: test_quick_consumer_name CONSUME_PASSIVELY CLUSTERING channel: ClientChannelInfo [channel=[id: 0x8a4e1302, L:/172.27.0.15:10911 - R:/125.78.209.60:26441], clientId=192.168.31.136@11976, language=JAVA, version=317, lastUpdateTimestamp=1582533184730]

2020-02-24 16:33:04 INFO HeartbeatThread_3 - subscription changed, add new topic, group: test_quick_consumer_name SubscriptionData [classFilterMode=false, topic=test_quick_topic, subString=*, tagsSet=[], codeSet=[], subVersion=1582533524972, expressionType=TAG]

2020-02-24 16:33:04 INFO HeartbeatThread_3 - subscription changed, add new topic, group: test_quick_consumer_name SubscriptionData [classFilterMode=false, topic=%RETRY%test_quick_consumer_name, subString=*, tagsSet=[], codeSet=[], subVersion=1582533525632, expressionType=TAG]

2020-02-24 16:33:04 INFO HeartbeatThread_3 - registerConsumer info changed ConsumerData [groupName=test_quick_consumer_name, consumeType=CONSUME_PASSIVELY, messageModel=CLUSTERING, consumeFromWhere=CONSUME_FROM_LAST_OFFSET, unitMode=false, subscriptionDataSet=[SubscriptionData [classFilterMode=false, topic=test_quick_topic, subString=*, tagsSet=[], codeSet=[], subVersion=1582533524972, expressionType=TAG], SubscriptionData [classFilterMode=false, topic=%RETRY%test_quick_consumer_name, subString=*, tagsSet=[], codeSet=[], subVersion=1582533525632, expressionType=TAG]]] 125.78.209.60:26441

2020-02-24 16:33:04 INFO HeartbeatThread_3 - new producer connected, group: CLIENT_INNER_PRODUCER channel: ClientChannelInfo [channel=[id: 0x8a4e1302, L:/172.27.0.15:10911 - R:/125.78.209.60:26441], clientId=192.168.31.136@11976, language=JAVA, version=317, lastUpdateTimestamp=1582533184730]

2020-02-24 16:33:04 INFO HeartbeatThread_4 - subscription changed, group: test_quick_consumer_name OLD: SubscriptionData [classFilterMode=false, topic=%RETRY%test_quick_consumer_name, subString=*, tagsSet=[], codeSet=[], subVersion=1582533525632, expressionType=TAG] NEW: SubscriptionData [classFilterMode=false, topic=%RETRY%test_quick_consumer_name, subString=*, tagsSet=[], codeSet=[], subVersion=1582533530514, expressionType=TAG]

2020-02-24 16:33:05 INFO HeartbeatThread_1 - subscription changed, group: test_quick_consumer_name OLD: SubscriptionData [classFilterMode=false, topic=test_quick_topic, subString=*, tagsSet=[], codeSet=[], subVersion=1582533524972, expressionType=TAG] NEW: SubscriptionData [classFilterMode=false, topic=test_quick_topic, subString=*, tagsSet=[], codeSet=[], subVersion=1582533530894, expressionType=TAG]

2020-02-24 16:33:05 INFO PullMessageThread_3 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_3 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_4 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_4 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_5 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_5 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_6 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_6 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_7 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_7 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_8 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_8 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_9 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_9 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_10 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_10 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_11 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_11 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_12 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_12 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_13 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_13 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_14 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_14 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_15 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_15 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_16 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_16 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_17 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_17 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_18 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_18 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_19 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_19 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_20 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_20 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_21 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_21 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_22 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_22 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_23 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_23 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_24 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_24 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_1 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_1 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_2 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_2 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_3 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_3 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_5 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 INFO PullMessageThread_4 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_5 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 WARN PullMessageThread_4 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_6 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_6 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_8 - the broker store no queue data, fix the request offset 2 to 2, Topic: test_quick_topic QueueId: 0 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_8 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=2, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_7 - the request offset: 4 over flow badly, broker max offset: 1, consumer: /125.78.209.60:26441

2020-02-24 16:33:05 WARN PullMessageThread_7 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=4, suggestBrokerId=0

2020-02-24 16:33:05 INFO PullMessageThread_9 - the broker store no queue data, fix the request offset 1 to 1, Topic: test_quick_topic QueueId: 1 Consumer Group: test_quick_consumer_name

2020-02-24 16:33:05 WARN PullMessageThread_9 - PULL_OFFSET_MOVED:none correction. topic=test_quick_topic, groupId=test_quick_consumer_name, requestOffset=1, suggestBrokerId=0


0 回复 有任何疑惑可以回复我~
收起回答
取消 回复
提问者 梨多情 2020-02-24 17:01:52

因此处字数受限，Slave 日志后续如下：

2020-02-24 16:32:23 ERROR BrokerControllerScheduledThread1 - SyncConsumerOffset Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllConsumerOffset(BrokerOuterAPI.java:348) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncConsumerOffset(SlaveSynchronize.java:84) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:50) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:23 ERROR BrokerControllerScheduledThread1 - SyncDelayOffset Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllDelayOffset(BrokerOuterAPI.java:365) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncDelayOffset(SlaveSynchronize.java:100) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:51) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:23 ERROR BrokerControllerScheduledThread1 - SyncSubscriptionGroup Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllSubscriptionGroupConfig(BrokerOuterAPI.java:382) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncSubscriptionGroupConfig(SlaveSynchronize.java:125) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:52) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:33 ERROR BrokerControllerScheduledThread1 - SyncTopicConfig Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10909> failed
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllTopicConfig(BrokerOuterAPI.java:331) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncTopicConfig(SlaveSynchronize.java:60) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:49) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:33 ERROR BrokerControllerScheduledThread1 - SyncConsumerOffset Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllConsumerOffset(BrokerOuterAPI.java:348) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncConsumerOffset(SlaveSynchronize.java:84) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:50) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:33 ERROR BrokerControllerScheduledThread1 - SyncDelayOffset Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllDelayOffset(BrokerOuterAPI.java:365) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncDelayOffset(SlaveSynchronize.java:100) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:51) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:33 ERROR BrokerControllerScheduledThread1 - SyncSubscriptionGroup Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllSubscriptionGroupConfig(BrokerOuterAPI.java:382) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncSubscriptionGroupConfig(SlaveSynchronize.java:125) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:52) [rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:40 INFO BrokerControllerScheduledThread1 - dispatch behind commit log 1025 bytes
2020-02-24 16:32:40 WARN brokerOutApi_thread_3 - registerBroker Exception, rocketmq-nameserver1:9876
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <rocketmq-nameserver1:9876> failed
at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.registerBroker(BrokerOuterAPI.java:194) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI.access$000(BrokerOuterAPI.java:61) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at org.apache.rocketmq.broker.out.BrokerOuterAPI$1.run(BrokerOuterAPI.java:150) ~[rocketmq-broker-4.5.2.jar:4.5.2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]

0 回复 有任何疑惑可以回复我~
收起回答
取消 回复
提问者 梨多情 2020-02-24 17:00:14

关闭 Master 后，启动 Consumer 进行消费，

此时，Slave 抛各种连接异常，紧接着死循环地重复刷警告日志，每秒刷几十次

Slave 节点的日志如下：

2020-02-24 16:32:13 ERROR BrokerControllerScheduledThread1 - SyncTopicConfig Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10909> failed
	at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllTopicConfig(BrokerOuterAPI.java:331) ~[rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncTopicConfig(SlaveSynchronize.java:60) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:49) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:13 ERROR BrokerControllerScheduledThread1 - SyncConsumerOffset Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
	at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllConsumerOffset(BrokerOuterAPI.java:348) ~[rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncConsumerOffset(SlaveSynchronize.java:84) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:50) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:13 ERROR BrokerControllerScheduledThread1 - SyncDelayOffset Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
	at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllDelayOffset(BrokerOuterAPI.java:365) ~[rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncDelayOffset(SlaveSynchronize.java:100) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:51) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:13 ERROR BrokerControllerScheduledThread1 - SyncSubscriptionGroup Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10911> failed
	at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllSubscriptionGroupConfig(BrokerOuterAPI.java:382) ~[rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncSubscriptionGroupConfig(SlaveSynchronize.java:125) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:52) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
2020-02-24 16:32:23 ERROR BrokerControllerScheduledThread1 - SyncTopicConfig Exception, 148.70.109.178:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to <148.70.109.178:10909> failed
	at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:392) ~[rocketmq-remoting-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.out.BrokerOuterAPI.getAllTopicConfig(BrokerOuterAPI.java:331) ~[rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncTopicConfig(SlaveSynchronize.java:60) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncAll(SlaveSynchronize.java:49) [rocketmq-broker-4.5.2.jar:4.5.2]
	at org.apache.rocketmq.broker.BrokerController$12.run(BrokerController.java:1120) [rocketmq-broker-4.5.2.jar:4.5.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_144]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_144]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
0 回复 有任何疑惑可以回复我~
收起回答
取消 回复

相似问题

生产消费后，master有消息，slave主节点一直是0/0；master挂掉后，slave无法消费
1719 1 6
主从配置，一主一从，producer.发送消息只到master节点，slave没有读到消息，master宕了，consuner没法消费到消息，配置和课程一样的。
1595 0 6
Consumer什么时候会从Slave中进行消费？
702 0 2
在slave docker container中尝试连接master但却变成了连接slave
1515 0 13
老师，多生产者消费之模式，使用RingBuffer，任务结束以后如何像 disruptor那样关闭了
1437 1 4

登录后可查看更多问答，登录/注册

问题已解决，确定采纳
还有疑问，暂不采纳
RocketMQ核心技术精讲与高并发抗压实战
  • 参与学习       1185    人
  • 解答问题       304    个

理论+实战，系统掌握RocketMQ核心技术, 挑战高并发抗压实战

了解课程

本课精华内容

问答

RemotingConnectException: connect to <172.17.0.1:10909> failed

10.8k 15

RemotingConnectException: connect to <172.17.0.1:10909> failed

10.8k 15

发送 异步消息时报错了

1.7k 11

老师，nameserver启动了，然后broker启动不了，日志也没有生成，不知道是什么原因

1.6k 7

主从配置，一主一从，producer.发送消息只到master节点，slave没有读到消息，master宕了，consuner没法消费到消息，配置和课程一样的。

1.6k 6

查看更多本课问答
微信客服

购课补贴
联系客服咨询优惠详情

 帮助反馈 APP下载

慕课网APP
您的移动学习伙伴

 公众号

扫描二维码
关注慕课网微信公众号