-
Notifications
You must be signed in to change notification settings - Fork 26.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DubboMetadataServiceProxy.removeProxy Lead to cpu 100% #7403
Comments
The complete stack information is |
I know the cause of this bug; We know the call situation through the top thread stack "com.alibaba.nacos.naming.client.listener" #459 daemon prio=5 os_prio=0 tid=0x00007f236d0d7000 nid=0x129b runnable [0x00007f23557fc000] When executing this code
jdk 8 ConcurrentHashMap Will initialize invoke initTable(); This will cause an null key to be placed inside and map an null finger
That’s why data like hashMap happened when I was debugging |
it seems as if is the issue of spring cloud alibaba? |
Then how do I transfer this question to the spring cloud alibaba project? |
I think the transfer has already been done, so close it first. |
Environment
The framework I user is spring cloud alibaba
The dubbo version information used internally is
The service registry uses nacos
Steps to reproduce this issue
I have two projects, A and B, and A depends on project B. When I started Project A, there was no problem.
Dubbo related configuration
But when I start project B, the nacos listener of project A will perform service subscription discovery processing when it is running. At this time, it will cause cpu 100% .
Note: No problems in development and test environment
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4763 prod 20 0 3908772 509644 16708 R 99.9 6.5 25:18.14 java
4279 prod 20 0 3908772 509644 16708 S 0.0 6.5 0:00.00 java
4281 prod 20 0 3908772 509644 16708 S 0.0 6.5 0:09.95 java
4282 prod 20 0 3908772 509644 16708 S 0.0 6.5 0:00.21 java
Stack information of the thread in question
The text was updated successfully, but these errors were encountered: