shirenchuang opened a new issue, #7402: URL: https://github.com/apache/rocketmq/issues/7402
### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary MQClientInstance#start  DefaultMQProducer 这个内部的生产者客户端只要在消费者客户端创建的时候才需要这个； **CLIENT_INNER_PRODUCER** 它的作用是在消费失败需要重试的时候，可以利用这个Producer将消息发送回去。 但是在创建生产者客户端的时候它并不需要这么一个内部的生产者客户端; 它没没有做任何事情，而且还占用了资源 --- 同理PullMessageService也是一样，在创建生产者客户端的时候它不需要使用到这个服务。 DefaultMQProducer This internal producer client only needs this when the consumer client is created; **CLIENT_INNER_PRODUCER** Its function is to use this Producer to send the message back when consumption fails and needs to be retried. But when you create a producer client, it doesn't need such an internal producer client; it doesn't do anything, and it also takes up resources. --- The same goes for PullMessageService. It does not need to use this service when creating a producer client. ### Motivation 1. 建议根据条件判断是否启用这些服务 2. 现在是不管什么客户端创建之后都会启动这些服务，连DashBoard这种毫无相关性的MQAdminExt客户端被创建时都启动了这些服务 3. MQClientInstance 秩序作为一个抽象的客户端实例就行了，只启动远程通信客户端能力即可。 4. 这些莫名其妙创建的客户端会带来一些困扰，比如`producer`命令查询所有生产者客户端的时候 列举了非常多的客户端 --- 1. It is recommended to determine whether to enable these services based on conditions 2. Now no matter what client is created, these services will be started. Even the unrelated MQAdminExt client like DashBoard starts these services when it is created. 3. MQClientInstance can be used as an abstract client instance, and only the remote communication client capability can be enabled. 4. These inexplicably created clients will cause some trouble. For example, when the `producer` command queries all producer clients, a lot of clients are listed. ### Describe the Solution You'd Like . ### Describe Alternatives You've Considered . ### 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]
