[Bug] Symptom: A single machine occasionally a large area of dubbo call timeout, only one machine a problem, for a few seconds, too late to view the thread blocking information, the problem passed, after the past all indicators are normal, the problem occurred within the time of cpu and memory and disk indicators are normal, traffic is not high. The Dubbo provider service uses jdk 11 and the garbage collector is G1. The log shows that the request has entered the dubbo provider service, but the next step is performed 3 seconds later. No log is found during these 3 seconds. safepoint shows that no exception is found and there are many biased locks

[yangshaotuo]

Pre-check

• I am sure that all the content I provide is in English.

Search before asking

• I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

Dubbo：2.7.17
JDK：11

Steps to reproduce this issue

A single machine occasionally a large area of dubbo call timeout, only one machine a problem, for a few seconds, too late to view the thread blocking information, the problem passed, after the past all indicators are normal, the problem occurred within the time of cpu and memory and disk indicators are normal, traffic is not high

What you expected to happen

The Dubbo provider service uses jdk 11 and the garbage collector is G1. The log shows that the request has entered the dubbo provider service, but the next step is performed 3 seconds later. No log is found during these 3 seconds. safepoint shows that no exception is found and there are many biased locks

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[AlbumenJ]

Check if there are some huge request / response. This will block your I/O thread.

[songxiaosheng]

If it can be reproduced, try packet capture analysis