broker master宕机卡死之后,client端还继续往broker 发送消息 #8226
BruceMiao305
started this conversation in
General
Replies: 1 comment
-
这个集群版本以及客户端版本都太老了,现在都5.2.0了。可能在客户端处理路由方面存在问题,建议升级到较新点的版本吧,例如4.9.x。 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
集群版本4.1.0 ,客户端版本3.2.6
现象:
其中一台物理机器卡死,nameserver包括客户端日志能看到remove卡死机器的broker master。
时间:8:56:20broker master卡死,客户端和nameserver都感知到了。
日志:
2024-05-28 09:08:54 INFO NettyClientWorkerThread_4 - closeChannel: the channel[172.16.168.14:16911] was removed from channel table
2024-05-28 09:08:54 INFO NettyClientWorkerThread_4 - NETTY CLIENT PIPELINE: CLOSE
2024-05-28 09:08:54 INFO NettyClientWorkerThread_4 - eventCloseChannel: the channel[null] has been removed from the channel table before
但是客户端还是一直会与挂掉的节点建立连接,重复的remove,所以很奇怪,麻烦大佬们帮忙看看,解答解答,或者又遇到类似现象的一起讨论一下。
Beta Was this translation helpful? Give feedback.
All reactions