You should investigate the cause of request-queue full situation first. Since I guess low network idle ratio is the consequence of that. (Network-threads would block on queueing when request-queue is full)
I recommend running async-profiler to take the profile of the broker process if possible (with wallclock mode). Then it will help you to identify the bottleneck which consuming request-handler time. 2024年1月15日(月) 17:58 dong yu <hideonbus...@gmail.com>: > This is my problem > 1.The request queue is always at 500 > 2.There are 130 machines in the cluster, and the network idle rate of 30 > machines is less than 20. > > > This is my BROKER configuration > num.io.threads=32 > num.network.threads=64 > > How should I locate the problem? I tried to increase the parameters but the > effect was not obvious. > THKS。 > -- ======================== Okada Haruki ocadar...@gmail.com ========================
