5.3.4版本什么时候发版啊

[john1337]

5.3.4版本什么时候发版啊，在使用5.3.3版本时发现不少问题，完全不能在生产环境使用

[leizhiyuan]

具体什么问题呢？如果有对应的 pr 修复，可以自己先合并回去打包。
What exactly is the problem? If there's a corresponding PR to fix it, you can merge it back and repackage it yourself first.

[john1337]

我采用的3主3从部署架构，master-slave角色切换后出现了topic not found的问题

[john1337]

查看出问题的broker上的broker.log日志文件，有一堆topic不存在的日志
ERROR AdminBrokerThread_9 - No topic in this broker, client: /10.233.103.153:51482 topic: xxxx
@leizhiyuan

[john1337]

具体报错的地方在AdminBrokerProcessor getTopic方法
private RemotingCommand getTopicConfig(ChannelHandlerContext ctx,
RemotingCommand request) throws RemotingCommandException {
GetTopicConfigRequestHeader requestHeader = (GetTopicConfigRequestHeader) request.decodeCommandCustomHeader(GetTopicConfigRequestHeader.class);
final RemotingCommand response = RemotingCommand.createResponseCommand(null);

   // 问题出处,本地缓存没有topicconfig数据直接就返回失败了
    TopicConfig topicConfig = this.brokerController.getTopicConfigManager().selectTopicConfig(requestHeader.getTopic());
    if (topicConfig == null) {
        LOGGER.error("No topic in this broker, client: {} topic: {}", ctx.channel().remoteAddress(), requestHeader.getTopic());
        //be care of the response code, should set "not-exist" explicitly
        response.setCode(ResponseCode.TOPIC_NOT_EXIST);
        response.setRemark("No topic in this broker. topic: " + requestHeader.getTopic());
        return response;
    }

TopicConfigManager类selectTopicConfig方法获取数据是从本地缓存获取的：
protected TopicConfig getTopicConfig(String topicName) {
// protected ConcurrentMap<String, TopicConfig> topicConfigTable = new ConcurrentHashMap<>(1024);
return this.topicConfigTable.get(topicName);
}

[zergduan]

Hi 请问这个问题解决了么？

我在5.3.4中进行了测试，主节点宕机的情况下，备节点依然无法提供消费功能（虽然不在报错： ERROR AdminBrokerThread_9 - No topic in this broker, client: /10.233.103.153:51482 topic: xxxx）

测试用例：

场景1：
NameServier、Broker = 5.3.3 (主备）
Client = 5.2

堆积消息在Topic:TP-FTEST-Normal的情况下主broker宕机，消费这使用消费组CG-FTEST-Normal对Topic:TP-FTEST-Normal中的堆积消息进行消费，发现无法消费成功（消费者日志中没有任何输出），并且在备Broker的broker.log中出现如下日志：

2025-11-28 11:23:08 WARN AdminBrokerThread_10 - AdminBrokerProcessor#getConsumeStats: topic config does not exist, topic=TP-FTEST-Normal
2025-11-28 11:23:08 ERROR AdminBrokerThread_2 - No topic in this broker, client: /10.177.96.150:44658 topic: TP-FTEST-Normal
2025-11-28 11:23:08 WARN AdminBrokerThread_15 - AdminBrokerProcessor#getConsumeStats: topic config does not exist, topic=TP-FTEST-Normal
2025-11-28 11:23:08 ERROR AdminBrokerThread_1 - No topic in this broker, client: /10.177.96.150:44658 topic: TP-FTEST-Normal
2025-11-28 11:23:24 INFO brokerOutApi_thread_4 - Registering current broker to name server completed. TargetHost=10.177.96.143:19876
2025-11-28 11:23:24 INFO brokerOutApi_thread_3 - Registering current broker to name server completed. TargetHost=10.177.96.144:19876
2025-11-28 11:23:26 INFO HeartbeatThread_2 - create new topic TopicConfig [topicName=%RETRY%CG-FTEST-Normal, readQueueNums=1, writeQueueNums=1, perm=RW-, topicFilterType=SINGLE_TAG, topicSysFlag=0, order=false, attributes={}]
2025-11-28 11:23:26 INFO brokerOutApi_thread_1 - Registering current broker to name server completed. TargetHost=10.177.96.144:19876
2025-11-28 11:23:26 INFO brokerOutApi_thread_2 - Registering current broker to name server completed. TargetHost=10.177.96.143:19876
2025-11-28 11:23:26 INFO HeartbeatThread_2 - new consumer connected, group: CG-FTEST-Normal CONSUME_PASSIVELY CLUSTERING channel: ClientChannelInfo [channel=[id: 0x646bfb2b, L:/10.177.96.146:22922 - R:/10.177.96.149:42584], clientId=10.177.96.149@10697#2588002808595, language=JAVA, version=477, lastUpdateTimestamp=1764300206686]
2025-11-28 11:23:26 INFO HeartbeatThread_2 - subscription changed, add new topic, group: CG-FTEST-Normal SubscriptionData [classFilterMode=false, topic=%RETRY%CG-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764300206128, expressionType=TAG]
2025-11-28 11:23:26 INFO HeartbeatThread_2 - subscription changed, add new topic, group: CG-FTEST-Normal SubscriptionData [classFilterMode=false, topic=TP-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764300206119, expressionType=TAG]
2025-11-28 11:23:26 INFO HeartbeatThread_2 - ClientManageProcessor: registerConsumer info changed, SDK address=10.177.96.149:42584, consumerData=ConsumerData [groupName=CG-FTEST-Normal, consumeType=CONSUME_PASSIVELY, messageModel=CLUSTERING, consumeFromWhere=CONSUME_FROM_FIRST_OFFSET, unitMode=false, subscriptionDataSet=[SubscriptionData [classFilterMode=false, topic=%RETRY%CG-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764300206128, expressionType=TAG], SubscriptionData [classFilterMode=false, topic=TP-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764300206119, expressionType=TAG]]]
2025-11-28 11:23:26 INFO HeartbeatThread_2 - new producer connected, group: CLIENT_INNER_PRODUCER channel: ClientChannelInfo [channel=[id: 0x646bfb2b, L:/10.177.96.146:22922 - R:/10.177.96.149:42584], clientId=10.177.96.149@10697#2588002808595, language=JAVA, version=477, lastUpdateTimestamp=1764300206688]
2025-11-28 11:23:27 INFO HeartbeatThread_2 - subscription changed, group: CG-FTEST-Normal OLD: SubscriptionData [classFilterMode=false, topic=TP-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764300206119, expressionType=TAG] NEW: SubscriptionData [classFilterMode=false, topic=TP-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764300207437, expressionType=TAG]
2025-11-28 11:23:27 INFO HeartbeatThread_1 - subscription changed, group: CG-FTEST-Normal OLD: SubscriptionData [classFilterMode=false, topic=%RETRY%CG-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764300206128, expressionType=TAG] NEW: SubscriptionData [classFilterMode=false, topic=%RETRY%CG-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764300207449, expressionType=TAG]
2025-11-28 11:23:53 INFO BrokerControllerScheduledThread1 - Dispatch task fall behind commit log 0bytes
2025-11-28 11:23:54 INFO brokerOutApi_thread_3 - Registering current broker to name server completed. TargetHost=10.177.96.144:19876
2025-11-28 11:23:54 INFO brokerOutApi_thread_4 - Registering current broker to name server completed. TargetHost=10.177.96.143:19876

场景2：
NameServier、Broker = 5.3.4 (主备）
Client = 5.2

堆积消息在Topic:TP-FTEST-Normal的情况下主broker宕机，消费这使用消费组CG-FTEST-Normal对Topic:TP-FTEST-Normal中的堆积消息进行消费，发现无法消费成功（消费者日志中没有任何输出），并且在备Broker的broker.log中出现如下日志（不再出现AdminBrokerProcessor#getConsumeStats: topic config does not exist和AdminBrokerThread_2 - No topic in this broker，但是备节点依然无法支持消费堆积消息 ）：

2025-11-28 14:28:07 INFO brokerOutApi_thread_1 - Registering current broker to name server completed. TargetHost=10.177.96.143:19876
2025-11-28 14:28:07 INFO brokerOutApi_thread_2 - Registering current broker to name server completed. TargetHost=10.177.96.144:19876
2025-11-28 14:28:07 INFO BrokerControllerScheduledThread1 - Update master address from 10.177.96.145:22922 to null
2025-11-28 14:28:37 INFO BrokerControllerScheduledThread1 - Dispatch task fall behind commit log 0bytes
2025-11-28 14:28:37 INFO brokerOutApi_thread_3 - Registering current broker to name server completed. TargetHost=10.177.96.143:19876
2025-11-28 14:28:37 INFO brokerOutApi_thread_4 - Registering current broker to name server completed. TargetHost=10.177.96.144:19876
2025-11-28 14:28:45 INFO HeartbeatThread_1 - new consumer connected, group: CG-FTEST-Normal CONSUME_PASSIVELY CLUSTERING channel: ClientChannelInfo [channel=[id: 0x562632be, L:/10.177.96.146:22922 - R:/10.177.96.149:45634], clientId=10.177.96.149@23409#13706546187932, language=JAVA, version=477, lastUpdateTimestamp=1764311325161]
2025-11-28 14:28:45 INFO HeartbeatThread_1 - subscription changed, add new topic, group: CG-FTEST-Normal SubscriptionData [classFilterMode=false, topic=%RETRY%CG-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764311324672, expressionType=TAG]
2025-11-28 14:28:45 INFO HeartbeatThread_1 - subscription changed, add new topic, group: CG-FTEST-Normal SubscriptionData [classFilterMode=false, topic=TP-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764311324664, expressionType=TAG]
2025-11-28 14:28:45 INFO HeartbeatThread_1 - ClientManageProcessor: registerConsumer info changed, SDK address=10.177.96.149:45634, consumerData=ConsumerData [groupName=CG-FTEST-Normal, consumeType=CONSUME_PASSIVELY, messageModel=CLUSTERING, consumeFromWhere=CONSUME_FROM_FIRST_OFFSET, unitMode=false, subscriptionDataSet=[SubscriptionData [classFilterMode=false, topic=%RETRY%CG-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764311324672, expressionType=TAG], SubscriptionData [classFilterMode=false, topic=TP-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764311324664, expressionType=TAG]]]
2025-11-28 14:28:45 INFO HeartbeatThread_1 - new producer connected, group: CLIENT_INNER_PRODUCER channel: ClientChannelInfo [channel=[id: 0x562632be, L:/10.177.96.146:22922 - R:/10.177.96.149:45634], clientId=10.177.96.149@23409#13706546187932, language=JAVA, version=477, lastUpdateTimestamp=1764311325161]
2025-11-28 14:28:45 INFO HeartbeatThread_1 - subscription changed, group: CG-FTEST-Normal OLD: SubscriptionData [classFilterMode=false, topic=TP-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764311324664, expressionType=TAG] NEW: SubscriptionData [classFilterMode=false, topic=TP-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764311325958, expressionType=TAG]
2025-11-28 14:28:45 INFO HeartbeatThread_2 - subscription changed, group: CG-FTEST-Normal OLD: SubscriptionData [classFilterMode=false, topic=%RETRY%CG-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764311324672, expressionType=TAG] NEW: SubscriptionData [classFilterMode=false, topic=%RETRY%CG-FTEST-Normal, subString=, tagsSet=[], codeSet=[], subVersion=1764311325973, expressionType=TAG]
2025-11-28 14:29:07 INFO brokerOutApi_thread_2 - Registering current broker to name server completed. TargetHost=10.177.96.144:19876
2025-11-28 14:29:07 INFO brokerOutApi_thread_1 - Registering current broker to name server completed. TargetHost=10.177.96.143:19876

[zergduan]

提交了一个BUG
#9879

目前依然没有解决~