[
https://issues.apache.org/jira/browse/KAFKA-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Harris updated KAFKA-16420:
--------------------------------
Description:
The Exit class is not thread-safe, and exposes our tests to race conditions and
inconsistent execution. It is not possible to make it thread-safe due to the
static design of the API.
We should migrate the existing usages to the replacement, before finally
removing the legacy Exit.
was:
The Exit class is not thread-safe, and exposes our tests to race conditions and
inconsistent execution. It is not possible to make it thread-safe due to the
static design of the API.
We should add an alternative to the Exit class, and migrate the existing usages
to the replacement, before finally removing the legacy Exit.
> Refactor utils.Exit call-sites to use thread-safe alternative
> -------------------------------------------------------------
>
> Key: KAFKA-16420
> URL: https://issues.apache.org/jira/browse/KAFKA-16420
> Project: Kafka
> Issue Type: Wish
> Components: connect, core, tools
> Reporter: Greg Harris
> Assignee: Greg Harris
> Priority: Minor
>
> The Exit class is not thread-safe, and exposes our tests to race conditions
> and inconsistent execution. It is not possible to make it thread-safe due to
> the static design of the API.
> We should migrate the existing usages to the replacement, before finally
> removing the legacy Exit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
