You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jhen Yung Hsu (Jira)" <ji...@apache.org> on 2024/10/27 21:40:00 UTC
[jira] [Assigned] (KAFKA-17883) Fix jvm error caused by UseParNewGC when running old kafka client in e2e
[ https://issues.apache.org/jira/browse/KAFKA-17883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jhen Yung Hsu reassigned KAFKA-17883:
-------------------------------------
Assignee: Jhen Yung Hsu (was: Chia-Ping Tsai)
> Fix jvm error caused by UseParNewGC when running old kafka client in e2e
> ------------------------------------------------------------------------
>
> Key: KAFKA-17883
> URL: https://issues.apache.org/jira/browse/KAFKA-17883
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Chia-Ping Tsai
> Assignee: Jhen Yung Hsu
> Priority: Major
>
> Fix JVM error caused by {{UseParNewGC}} when running an old Kafka client in E2E tests. The old JVM config options like {{UseParNewGC}} were removed in JDK 11 (see [JDK-8151084|https://bugs.openjdk.org/browse/JDK-8151084]), so we need to update the JVM options used to run the old Kafka client. A helper function, {{{}fix_opts_for_new_jvm{}}}, is available to add suitable JVM configurations for the old Kafka client. {{{}ConsumerPerformanceService{}}}, {{{}EndToEndLatencyService{}}}, and {{ProducerPerformanceService}} need to be updated accordingly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)