[
https://issues.apache.org/jira/browse/KAFKA-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-19912:
------------------------------
Description: Builds of Kafka began failing in the GitHub Actions
environment because of an OOM error. KAFKA-19898 was filed and one of the
client unit tests was identified as the culprit. [A
fix|https://github.com/apache/kafka/pull/20930] was pushed quickly to resolve
the issue. However, since the test is only executed once per run, it's not
clear how a small number of dangling threads could have caused the entire build
to experience problems. (was: Builds of Kafka began failing in the GitHub
Actions environment because of an OOM error. An issue was identified in one of
the client unit tests and [a fix|https://github.com/apache/kafka/pull/20930]
was pushed quickly to resolve the issue. However, since the test is only
executed once per run, it's not clear how a small number of dangling threads
could have caused the entire build to experience problems.)
> Investigate OOM error on builds due to leaded thread
> ----------------------------------------------------
>
> Key: KAFKA-19912
> URL: https://issues.apache.org/jira/browse/KAFKA-19912
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer, unit tests
> Reporter: Kirk True
> Assignee: Kirk True
> Priority: Major
>
> Builds of Kafka began failing in the GitHub Actions environment because of an
> OOM error. KAFKA-19898 was filed and one of the client unit tests was
> identified as the culprit. [A fix|https://github.com/apache/kafka/pull/20930]
> was pushed quickly to resolve the issue. However, since the test is only
> executed once per run, it's not clear how a small number of dangling threads
> could have caused the entire build to experience problems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
