ijuma commented on PR #19138:
URL: https://github.com/apache/kafka/pull/19138#issuecomment-2704699854
Looks like @lianetm is currently away. Since @chia7712 reviewed this too,
please go ahead and merge when you're ready @dajac
--
This is an automated message from the Apache Git Service.
dajac merged PR #19138:
URL: https://github.com/apache/kafka/pull/19138
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.or
dajac commented on PR #19138:
URL: https://github.com/apache/kafka/pull/19138#issuecomment-2705797666
Cherry-picked it to 4.0 and 3.9.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
dajac commented on PR #19138:
URL: https://github.com/apache/kafka/pull/19138#issuecomment-2703390355
The `LogContext` is also used by `FetchSessionHandler` but those are created
less frequently. Hence, we can keep it as it is.
--
This is an automated message from the Apache Git Service.
dajac opened a new pull request, #19138:
URL: https://github.com/apache/kafka/pull/19138
This patch is a first step towards resolving KAFKA-18046. Apache Kafka 4.0
ships with log4j2 so the issue raised in the ticket causing high CPU usage on
the fetch path due to LoggerFactory.getLogger() b
