[
https://issues.apache.org/jira/browse/KAFKA-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304224#comment-15304224
]
Eno Thereska commented on KAFKA-3637:
-------------------------------------
It turns out it might not make sense to have an "initialised" concept for
streams, since partitions can be reassigned to stream tasks any time, and also
it might take time for the initial partitions to be assigned at all. There is a
simpler way to fix KAFKA-3678.
> Add method that checks if streams are initialised
> -------------------------------------------------
>
> Key: KAFKA-3637
> URL: https://issues.apache.org/jira/browse/KAFKA-3637
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Eno Thereska
> Assignee: Liquan Pei
> Labels: newbie
> Fix For: 0.10.1.0
>
>
> Currently when streams are initialised and started with streams.start(),
> there is no way for the caller to know if the initialisation procedure
> (including starting tasks) is complete or not. Hence, the caller is forced to
> guess for how long to wait. It would be good to have a way to return the
> state of the streams to the caller.
> One option would be to follow a similar approach in Kafka Server
> (BrokerStates.scala).
> As part of this change, we must remove the Thread.sleep() call in the Kafka
> Streams integration tests and substitute it with TestUtils.waitUntilTrue().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
