You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Stanislav Kozlovski (Jira)" <ji...@apache.org> on 2020/08/04 14:10:00 UTC
[jira] [Resolved] (KAFKA-10353) Trogdor - Fix RoundTripWorker to
not fail when the topic it's trying to create already exists
[ https://issues.apache.org/jira/browse/KAFKA-10353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stanislav Kozlovski resolved KAFKA-10353.
-----------------------------------------
Resolution: Duplicate
> Trogdor - Fix RoundTripWorker to not fail when the topic it's trying to create already exists
> ---------------------------------------------------------------------------------------------
>
> Key: KAFKA-10353
> URL: https://issues.apache.org/jira/browse/KAFKA-10353
> Project: Kafka
> Issue Type: Bug
> Reporter: Stanislav Kozlovski
> Priority: Major
>
> Trogdor's RoundTripWorker calls WorkerUtils#createTopics with a failOnCreate flag equal to true, making the code throw an exception if the topic already exists.
> [https://github.com/apache/kafka/blob/28b7d8e21656649fb09b09f9bacfe865b0ca133c/tools/src/main/java/org/apache/kafka/trogdor/workload/RoundTripWorker.java#L149]
> This is prone to race conditions when scheduling multiple workers to start at the same time - only one will succeed in creating a topic and running the test, while the rest will end up with a fatal error
> This has also been seen to happen in the RoundTripFaultTest system test where a network exception can cause the CreateTopics request to reach Kafka but Trogdor retry it and hit a TopicAlreadyExists exception on the retry, failing the test.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)