I have seen very high "Fetch-Consumer-RequestsPerSec" (like 15K) per broker in a relatively idle cluster. My hypothesis some misbehaving consumer has a tight polling loop without any back-off logic with empty fetch.
Unfortunately, this metric doesn't have per-topic breakdown like "BytesInPerSec" or "MessagesInPerSec". So I can't really tell which topic/consumer is pounding the cluster. Also the storm already ended. So I can't use tcpdump to capture live traffic. So any suggestion?
