[Enhancement] When there are too many consumers and there are too many RocketMQ client threads

[imgoby]

Before Creating the Enhancement Request

• I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

When there are too many consumers and there are too many RocketMQ client threads, details:
NettyClientWorkerThread_1: 4746 threads
Client House Keeping Service: 2373 threads
CleanExpireMsgSchechedThread_: 4378 threads
RebalanceServic: 2373 threads
NettyClientSele: 2373 threads

How to resolve?

Motivation

reduce threads, reduce memory.

Describe the Solution You'd Like

Merge timers, schedule executor

Describe Alternatives You've Considered

Merge timers, schedule executor

Additional Context

No response

[yx9o]

Hi, I want to know how the client is used. Will multiple consumers be created in the same process?

[imgoby]

yes. in the same process. it is a rocketmq client. the process is a java application using springboot+rocketmq
For example, there is a topic: hello_topic， Then there were 3000 consumers who consumed the topic according to the conditions and found that the process memory occupied 10G

[yx9o]

Is instanceName set?

[imgoby]

No, can this parameter solve it?

[Yelijah]

Rocketmq grpc client will create a thread pool for every consumer or producer. So I modify the client source code to fix this problem。