5.3版本 controller模式，两个broker,有一个是不同步副本

[lixiang365]

版本5.3.0
docker 部署
三个namesrv, 每个都打开了controller
两个broker, 都打开了proxy

#brokerName	broker-a
#MasterBrokerId	1
#MasterAddr	10.99.155.247:10911
#MasterEpoch	5
#SyncStateSetEpoch	2
#SyncStateSetNums	1

InSyncReplica:	ReplicaIdentity{brokerName='broker-a', brokerId=1, brokerAddress='10.99.155.247:10911', alive=true}

NotInSyncReplica:	ReplicaIdentity{brokerName='broker-a', brokerId=2, brokerAddress='10.99.155.248:11911', alive=true}

部署完就是这样。
日志没有报错
这个问题该如何解决？目前不会自动切换

补充broker1 日志

2024-10-11 15:55:02 INFO brokerOutApi_thread_4 - Registering current broker to name server completed. TargetHost=mqnamesrv:9876
2024-10-11 15:55:02 INFO brokerOutApi_thread_2 - Registering current broker to name server completed. TargetHost=10.99.155.248:9877
2024-10-11 15:55:02 INFO brokerOutApi_thread_3 - Registering current broker to name server completed. TargetHost=10.99.155.248:9876
2024-10-11 15:55:05 INFO ReplicasManager_ScheduledService_3 - Update controller leader address to 10.99.155.248:9812
2024-10-11 15:55:05 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/acl is not exist
2024-10-11 15:55:10 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/acl is not exist
2024-10-11 15:55:15 INFO ReplicasManager_ScheduledService_1 - Update controller leader address to 10.99.155.248:9812
2024-10-11 15:55:15 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/acl is not exist
2024-10-11 15:55:20 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/acl is not exist
2024-10-11 15:55:25 INFO ReplicasManager_ScheduledService_3 - Update controller leader address to 10.99.155.248:9812
2024-10-11 15:55:25 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/acl is not exist
2024-10-11 15:55:30 INFO BrokerControllerScheduledThread1 - Dispatch task fall behind commit log 0byte

补充broker2日志

2024-10-11 15:53:07 INFO brokerOutApi_thread_2 - Registering current broker to name server completed. TagetHost=10.99.155.247:9876
2024-10-11 15:53:10 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/ac is not exist
2024-10-11 15:53:10 INFO ReplicasManager_ScheduledService_1 - Update controller leader address to 10.99.55.248:9812
2024-10-11 15:53:13 INFO BrokerControllerScheduledThread1 - Update slave topic config from master, 10.99155.247:10911
2024-10-11 15:53:13 INFO BrokerControllerScheduledThread1 - Update slave consumer offset from master, 1099.155.247:10911
2024-10-11 15:53:13 INFO BrokerControllerScheduledThread1 - load /home/rocketmq/store/config/delayOffsetjson OK
2024-10-11 15:53:13 INFO BrokerControllerScheduledThread1 - Update slave delay offset from master, 10.99155.247:10911
2024-10-11 15:53:13 INFO BrokerControllerScheduledThread1 - Update slave Message Request Mode from maste, 10.99.155.247:10911
2024-10-11 15:53:15 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/ac is not exist
2024-10-11 15:53:20 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/ac is not exist
2024-10-11 15:53:20 INFO ReplicasManager_ScheduledService_2 - Update controller leader address to 10.99.55.248:9812
2024-10-11 15:53:25 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/ac is not exist
2024-10-11 15:53:25 INFO BrokerControllerScheduledThread1 - Update slave topic config from master, 10.99155.247:10911
2024-10-11 15:53:25 INFO BrokerControllerScheduledThread1 - Update slave consumer offset from master, 1099.155.247:10911
2024-10-11 15:53:25 INFO BrokerControllerScheduledThread1 - load /home/rocketmq/store/config/delayOffsetjson OK
2024-10-11 15:53:25 INFO BrokerControllerScheduledThread1 - Update slave delay offset from master, 10.99155.247:10911
2024-10-11 15:53:25 INFO BrokerControllerScheduledThread1 - Update slave Message Request Mode from maste, 10.99.155.247:10911
2024-10-11 15:53:30 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/ac is not exist
2024-10-11 15:53:30 INFO ReplicasManager_ScheduledService_2 - Update controller leader address to 10.99.55.248:9812
2024-10-11 15:53:35 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/ac is not exist
2024-10-11 15:53:37 INFO brokerOutApi_thread_2 - Registering current broker to name server completed. TagetHost=10.99.155.248:9877
2024-10-11 15:53:37 INFO brokerOutApi_thread_1 - Registering current broker to name server completed. TagetHost=10.99.155.248:9876
2024-10-11 15:53:37 INFO brokerOutApi_thread_3 - Registering current broker to name server completed. TagetHost=10.99.155.247:9876
2024-10-11 15:53:37 INFO BrokerControllerScheduledThread1 - Update slave topic config from master, 10.99155.247:10911
2024-10-11 15:53:37 INFO BrokerControllerScheduledThread1 - Update slave consumer offset from master, 1099.155.247:10911
2024-10-11 15:53:37 INFO BrokerControllerScheduledThread1 - load /home/rocketmq/store/config/delayOffsetjson OK
2024-10-11 15:53:37 INFO BrokerControllerScheduledThread1 - Update slave delay offset from master, 10.99155.247:10911
2024-10-11 15:53:37 INFO BrokerControllerScheduledThread1 - Update slave Message Request Mode from maste, 10.99.155.247:10911
2024-10-11 15:53:40 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/ac is not exist
2024-10-11 15:53:40 INFO ReplicasManager_ScheduledService_3 - Update controller leader address to 10.99.55.248:9812

关闭broker1, broker2日志 就会出现无法选举主节点

2024-10-11 15:58:55 INFO AclFileWatchService - The default acl dir /home/rocketmq/rocketmq-5.3.0/conf/acl is not exist
2024-10-11 15:58:55 ERROR BrokerControllerScheduledThread1 - syncTimerCheckPoint Exception, 10.99.155.247:10911
org.apache.rocketmq.remoting.exception.RemotingConnectException: connect to 10.99.155.247:10909 failed
	at org.apache.rocketmq.remoting.netty.NettyRemotingClient.invokeSync(NettyRemotingClient.java:574)
	at org.apache.rocketmq.broker.out.BrokerOuterAPI.getTimerCheckPoint(BrokerOuterAPI.java:786)
	at org.apache.rocketmq.broker.slave.SlaveSynchronize.syncTimerCheckPoint(SlaveSynchronize.java:208)
	at org.apache.rocketmq.broker.controller.ReplicasManager.lambda$handleSlaveSynchronize$2(ReplicasManager.java:361)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	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)
2024-10-11 15:58:55 ERROR ReplicasManager_ScheduledService_3 - Failed to try elect
org.apache.rocketmq.client.exception.MQBrokerException: CODE: 2012  DESC: Failed to elect a new master
For more information, please visit the url, https://rocketmq.apache.org/docs/bestPractice/06FAQ
	at org.apache.rocketmq.broker.out.BrokerOuterAPI.brokerElect(BrokerOuterAPI.java:1276)
	at org.apache.rocketmq.broker.controller.ReplicasManager.brokerElect(ReplicasManager.java:378)
	at org.apache.rocketmq.broker.controller.ReplicasManager.lambda$schedulingSyncBrokerMetadata$3(ReplicasManager.java:663)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	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)

[luozongle01]

应该是因为broker2不在SyncStateSet中，不在SyncStateSet中是broker1认为broker2和自己的差异过大。应该先需要解决broker2不在SyncStateSet的问题。
这是新部署的吗，里面没有数据吗？
部署完之后没有发送消息 broker2他就不在SyncStateSet中吗？

[lixiang365]

第一个在面板里显示是主节点，第二个是从节点

[luozongle01]

第一个在面板里显示是主节点，第二个是从节点

老哥要不加个好友，我也挺好奇这个问题的，这上面聊太慢了 😂

[lixiang365]

好呀这个图片不显示,你加我 wx ，bHRsODUyMQ==

[onejimmyboy]

好呀这个图片不显示,你加我 wx ，bHRsODUyMQ==

老哥，找到问题了可以贴一下解决方案啊，我之前在部署虚拟机版的时候也发现过

[luozongle01]

好呀这个图片不显示,你加我 wx ，bHRsODUyMQ==

老哥，找到问题了可以贴一下解决方案啊，我之前在部署虚拟机版的时候也发现过

需要在broker配置文件中配置下brokerIP2的地址，主从复制用的是brokerIP2，容器环境下brokerIP2容易获取到一个其他容器不可访问的地址