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

   ### 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
   
   ### RocketMQ version
   
   5.1.1
   
   ### JDK Version
   
   1.8
   
   ### Describe the Bug
   
   The architecture consists of three data centers, three brokers, one master, 
and two slaves. Three controllers are also one for each data center (the same 
as the nameserver).
   
   Simulate the isolation of the broker master and one controller network from 
the brokers and controllers of the other two data centers.
   
   During network failures, it can be observed that two broker masters will 
appear, and when the network is restored, the original master will become a 
slave.
   
   However, messages sent to the original master during network failures will 
be lost.
   
   ### Steps to Reproduce
   
   1,Simulate the isolation of the broker master and one controller network 
from the brokers and controllers of the other two data centers.
   2,send message to the original master
   
   ### What Did You Expect to See?
   
   Sending a message to the original master that has been quarantined should 
result in an error
   
   ### What Did You See Instead?
   
   Sending a message to the original master that has been quarantined did not 
report an error
   
   ### 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to