[Bug] CONSUMER_SEND_MSG_BACK request may be sent to ns

[yx9o]

Before Creating the Bug Report

• I found a bug, not just asking a question, which should be created in GitHub Discussions.

• I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

• I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

linux

RocketMQ version

all

JDK Version

jdk1.8

Describe the Bug

In some scenarios, for example,

• In master-slave mode, after the master fails, the slave node will consume data. If consumption fails, it will be sent back to the master broker. At this time, there is no master in the routing information, and the result is null. The request will be sent to ns.
• In master-slave mode, when the master fails and recovers, the producer gets the routing information before the consumer. At this time, the producer sends data to the master, and the consumer consumes data on the slave node. If consumption fails, it will be sent back to the master broker. At this time, there is no master in the routing information, and the result is null. The request will be sent to ns.

Steps to Reproduce

In master-slave mode, simulated consumption fails and returns ConsumeConcurrentlyStatus.RECONSUME_LATER
At this time, if you stop the master node, you will find that there is a request to send network ns.

What Did You Expect to See?

CONSUMER_SEND_MSG_BACK requests are only sent to brokers.

What Did You See Instead?

CONSUMER_SEND_MSG_BACK request is sent to ns.

Additional Context

No response