controller通知broker变更失败，导致两个broker一直是master #6869
Replies: 1 comment 4 replies
-
看是controller没有连接上broker。这个到不会有太大影响，角色变更会依赖2点来保证：1. controller反向通知broker 2.broker定时会向controller同步元数据信息。即使1失败了，2仍然会起作用。保证角色变更完成 |
Beta Was this translation helpful? Give feedback.
-
|
嗯是的，但是broker-a和broker-b都把自己变更成了master ... ,在看板中也是两个broker都是master... 0.0 这是broker-a的变更日志：
这是broker-b的变更日志：
以下分别是broker-a和broker-b的配置文件:
还有broker对namesrc和controller的连接也是好的，日志如下：
controller集群状态也是好的，执行命令后如下：
|
Beta Was this translation helpful? Give feedback.
-
|
从日志上看，两个broker都进入了一次这个方法 public void changeToMaster(final int newMasterEpoch, final int syncStateSetEpoch, final Set<Long> syncStateSet)之后日志也不打印了，可能是因为有这个限制把 public void changeToMaster(final int newMasterEpoch, final int syncStateSetEpoch, final Set<Long> syncStateSet) {
synchronized (this) {
if (newMasterEpoch > this.masterEpoch) {
...
}
}
public void changeToSlave(final String newMasterAddress, final int newMasterEpoch, Long newMasterBrokerId) {
synchronized (this) {
if (newMasterEpoch > this.masterEpoch) {
...
}
}然后因为controller主动通知变更角色失败了，两个broker就一直是master了... |
Beta Was this translation helpful? Give feedback.
-
|
这是controller通知broker变更角色失败的完整日志： localAddress 是 UNKNOWN |
Beta Was this translation helpful? Give feedback.
-
如果你需要一主一备，则需要使得两个broker配置文件中的brokerName是相同的。但从上面的描述看，两个broker的brokerName并不相同，因此会选出两个主来 |
Beta Was this translation helpful? Give feedback.
-
broker监听端口是10911，然后服务都是正常了，日志都没有报错。但是在controller通知broker变更角色的时候，提示这个错误。可以帮忙看下是什么原因吗？
2023-06-07 18:01:44 ERROR ControllerManager_NotifyService_2 - Failed to notify broker 192.168.105.104:10911 that role changed org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to failed at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeOneway(NettyRemotingClient.java:759) at org.apache.rocketmq.controller.ControllerManager.doNotifyBrokerRoleChanged(ControllerManager.java:210) at org.apache.rocketmq.controller.ControllerManager$NotifyService.lambda$notifyBroker$0(ControllerManager.java:302) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750)Beta Was this translation helpful? Give feedback.
All reactions