[Bug] getSystemTopicList Only Returns One Master-Slave System Synchronization Topic in Two-Master-Two-Slave Mode
Before Creating the Bug Report
-
[x] I found a bug, not just asking a question, which should be created in GitHub Discussions.
-
[x] I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
-
[x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
docker amd64 centos7.9
RocketMQ version
rocketmq5.3.2
JDK Version
jdk8
Describe the Bug
In the current two-master-two-slave deployment mode, when calling the getSystemTopicList API, it is found that only one master-slave system synchronization topic named “rmg sys SYNC BROKER MEMBER broker-b” is returned. This behavior is not as expected, and it is expected to return a list of all system synchronization topics.
Steps to Reproduce
a.Make sure the system is in a two-master-two-slave deployment mode b.Call the getSystemTopicList API to get the list of system synchronization topics c.Observe the return results and find that only “rmg_sys_SYNC_BROKER_MEMBER_broker-b” is included
What Did You Expect to See?
It is expected that getSystemTopicList can return all topics related to system synchronization, not just a single master-slave topic.
What Did You See Instead?
The actual return result only contains the one like “rmg_sys_SYNC_BROKER_MEMBER_broker-b” topic.
Additional Context
No response