You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "John Roesler (Jira)" <ji...@apache.org> on 2020/06/29 18:01:00 UTC

[jira] [Commented] (KAFKA-10194) run the reset tool between stopping StreamsOptimizedTest and starting the new one

    [ https://issues.apache.org/jira/browse/KAFKA-10194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148030#comment-17148030 ] 

John Roesler commented on KAFKA-10194:
--------------------------------------

Hey [~chia7712] , can we just include this work in the scope of https://issues.apache.org/jira/browse/KAFKA-10191 ?

> run the reset tool between stopping StreamsOptimizedTest and starting the new one
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-10194
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10194
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams, system tests
>            Reporter: Chia-Ping Tsai
>            Priority: Minor
>              Labels: newbie
>
> inspired by [~ableegoldman]
> {quote}
> So, that's exactly what we should do in this test. We need to
> 1. call KafkaStreams#cleanup before starting the application up the second time (ie when we turn optimizations on)
> 2. run the reset tool between stopping the original application and starting the new one
> I think that 1. alone would technically be enough to stop this test from failing, but we should really be doing both. 
> {quote}
> the comment.1 is addressed by KAFKA-10191 and this issue aims to address another one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)