[
https://issues.apache.org/jira/browse/KAFKA-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297520#comment-17297520
]
Peter Sinoros-Szabo commented on KAFKA-12431:
---------------------------------------------
Yes, it is about 500ms until it returns the data.
We just found the reason for this behaviour. Quota for all users were set to 0
like this:
kafka-configs.sh --zookeeper test-zk:2181 --alter --add-config
'producer_byte_rate=0, consumer_byte_rate=0, request_percentage=1000'
--entity-type users --entity-default
It was working fine on 2.4.1. Our intention with enabling quotas this way was
to not use quotas but enable some useful metrics that is there only if quota is
"on". But it seems that since 2.5 the broker uses these settings differently
and actually blocks the client for 500ms.
After we set the producer_byte_rate and consumer_byte_rate values to a high
enough value, everything is working again as expected.
So, for us setting the high values is just fine.
I don't know if this behaviour is how it should work or maybe this is still a
small bug, please close the ticket if this is how it should work.
> Fetch Request/Response without Topic information
> ------------------------------------------------
>
> Key: KAFKA-12431
> URL: https://issues.apache.org/jira/browse/KAFKA-12431
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.6.1
> Reporter: Peter Sinoros-Szabo
> Priority: Major
> Attachments: fetch-on-2.4.1.png, fetch-on-2.6.1.png,
> kafka-highcpu-24.svg.zip, kafka-highcpu-26.svg.zip
>
>
> I was running a 6 node Kafka 2.4.1 cluster with protocol and message format
> version set to 2.4. I wanted to upgrade the cluster to 2.6.1 and after I
> upgraded the 1st broker to 2.6.1 without any configuration change, I noticed
> much higher CPU usage on that broker (instead of 25% CPU usage it was ~350%)
> and about 3-4x higher network traffic. So I dumped the traffic between the
> Kafka client and broker and compared it with the traffic of the same broker
> downgraded to 2.4.1.
> It seems to me that after I upgraded to 2.6.1, the Fetch requests and
> responses are not complete, it is missing the topics part of the Fetch
> Request, I don't know for what reason. I guess there should be always a
> topics part.
> I'll attache a screenshot from these messages.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
