The thread too much

[gaoguofan]

Describe the bug
When using dubbo to integrate with nacos, there are a lot of different types of threads found.

Expected behavior
According to common sense, the role of this part of the thread pool is inferred. The first is to publish the heartbeat of the interface, and the other is to obtain interface data through long polling.But the number of these two threads should not be too much, a single thread is enough to traverse the status of all interfaces and the business of heartbeat

Actually behavior
A clear and concise description of what you actually to happen.
The version of the nacos client I am using is 1.2, and the names of these two threads are “com.alibaba.nacos.client.naming.updater” and com.alibaba.nacos.naming.beat.sender

[WilliamsSj]

We confirm that the bug exists and we plan to fix it in the advanced 3.0 release.

[KomachiSion]

you can update to 2.0 version, in 2.0 version the heartbeat is connection level, not interface level.

[KomachiSion]

and you can see whether you use dubbo 2.7.8, which has bugs to create quick many threads.

[ijustyce]

can you give me some link about this question please.

[gaoguofan]

No link yet, but I can give you a description of the scenario I use.
I used a self-developed gateway and needed to consume multiple dubbo interfaces. At this time, there will be many threads related to nacos, such as idle, sender threads, etc.
I found through source code analysis that when each dubbo interface generates an agent, a thread pool of 8 threads will be created. Note that every dubbo interface will do this, but I found through source code analysis that the relevant parameters are configured in registryConfig , the number of threads in the generated thread pool can be stabilized at 1, and the configuration parameters are as follows:

[gaoguofan]

can you give me some link about this question please.

see above

[KomachiSion]

apache/dubbo#6988