Details
Description
In rare situations and under heavy load (> 100 fetcher threads) I've seen that the protocol-okhttp plugin gets into a state where a significant amount of CPU time is spent in handling failed connections, see async-profiler screenshot. This is caused by okhttp#5819 which is fixed with okhttp 4.5.0).
We should upgrade to the okhttp 4.9.1 (the current stable version).
Attachments
Attachments
Issue Links
- links to