fujian-zfj opened a new issue, #6508: URL: https://github.com/apache/rocketmq/issues/6508
The issue tracker is used for bug reporting purposes **ONLY** whereas feature request needs to follow the [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal). To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one. It is recommended to start a discussion thread in the [mailing lists](http://rocketmq.apache.org/about/contact/) or [github discussions](https://github.com/apache/rocketmq/discussions) in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues. We welcome any friendly suggestions, bug fixes, collaboration, and other improvements. Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself. Generally, fixing an issue goes through the following steps: 1. Understand the issue reported; 1. Reproduce the unexpected behavior locally; 1. Perform root cause analysis to identify the underlying problem; 1. Create test cases to cover the identified problem; 1. Work out a solution to rectify the behavior and make the newly created test cases pass; 1. Make a pull request and go through peer review; As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints: **BUG REPORT** 1. Please describe the issue you observed: I notice a bug in the following case. 1. start two broker, one acting as master(node1), the other acting as slave(node2) 2. first kill node1, then node2 will change to master 3. right after node2 changing to master(node2 has not register to namesrv), kill node2 4. then client send messages(msg1 to msg100) to topic1 and subscribe topic1 successfully 5. two minutes later, node1 start, due to node1 is not in syncStateSet, it can not be elected as master 6. ten minutes later, node2 start and is elected as master, then node1 change to slave and truncate dirty message (msg1 to msg100) In step 4, the reason that client can successfully send message to node1 is that namesrv still think the master is node1. So wh should prohibit writing and reading before confirming the broker role in ha mode 8. Please tell us about your environment: 9. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc): **FEATURE REQUEST** 1. Please describe the feature you are requesting. 2. Provide any additional detail on your proposed use case for this feature. 3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue? 10. If there are some sub-tasks involved, use -[] for each sub-task and create a corresponding issue to map to the sub-task: - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here, - ... -- 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]
