[
https://issues.apache.org/jira/browse/KAFKA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759285#comment-17759285
]
Lucas Bradstreet commented on KAFKA-15402:
------------------------------------------
I had a brief look at the code in the profile and I think the most likely cause
is the fix for https://issues.apache.org/jira/browse/KAFKA-7109. That change
added an extra phase in consumer close where fetch sessions on the broker would
be requested to be closed/cleared.
If you comment out the call to maybeCloseFetchSessions, it looks like it'd
restore the old behavior where they'd be left on the broker. If you're able to
confirm that the close performs similarly with that line commented out we can
work from there.
> Performance regression on close consumer after upgrading to 3.5.0
> -----------------------------------------------------------------
>
> Key: KAFKA-15402
> URL: https://issues.apache.org/jira/browse/KAFKA-15402
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 3.5.0, 3.5.1
> Reporter: Benoit Delbosc
> Priority: Major
> Attachments: image-2023-08-24-18-51-21-720.png,
> image-2023-08-24-18-51-57-435.png, image-2023-08-25-10-50-28-079.png
>
>
> Hi,
> After upgrading to Kafka client version 3.5.0, we have observed a significant
> increase in the duration of our Java unit tests. These unit tests heavily
> rely on the Kafka Admin, Producer, and Consumer API.
> When using Kafka server version 3.4.1, the duration of the unit tests
> increased from 8 seconds (with Kafka client 3.4.1) to 18 seconds (with Kafka
> client 3.5.0).
> Upgrading the Kafka server to 3.5.1 show similar results.
> I have come across the issue KAFKA-15178, which could be the culprit. I will
> attempt to test the proposed patch.
> In the meantime, if you have any ideas that could help identify and address
> the regression, please let me know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
