frinda opened a new issue, #7264:
URL: https://github.com/apache/rocketmq/issues/7264

   ### Before Creating the Bug Report
   
   - [X] I found a bug, not just asking a question, which should be created in 
[GitHub Discussions](https://github.com/apache/rocketmq/discussions).
   
   - [X] I have searched the [GitHub 
Issues](https://github.com/apache/rocketmq/issues) and [GitHub 
Discussions](https://github.com/apache/rocketmq/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
   
   SUSE Linux Enterprise Server 12 SP5
   
   ### RocketMQ version
   
   develop|4.9.x
   
   ### JDK Version
   
   JDK 1.8.0_372
   
   ### Describe the Bug
   
   In active/standby mode, when I run command 'mqadmin deleteTopic -b xxx -t 
xxx'  to delete unused topic,  topic consume queue on the standby node is not 
deleted synchronously
   
   ### Steps to Reproduce
   
   1. Deploying the active/standby Mode Environment
   2. Send and consume messages with the topic 'test001'  in push mode at the 
same time, run a while(About two or five minutes)
   3. stop producer and consumer, run command ‘mqadmin deleteTopic -b xxx 
-test001’ to delete topic 'test001'
   
   ### What Did You Expect to See?
   
   topic consume queue on the standby node is still exist.
   
![image](https://github.com/apache/rocketmq/assets/9562305/159678e4-044a-4c50-84fc-a8f98f3eb2b2)
   
   
   ### What Did You See Instead?
   
   Delete all the information about this topic from the active/standby.
   
   ### Additional Context
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to