[
https://issues.apache.org/jira/browse/KAFKA-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eno Thereska updated KAFKA-3637:
--------------------------------
Description:
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).
Would be good for example, to keep track of whether Kafka Streams is
starting/running/rebalancing
was:
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().
> 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: Eno Thereska
> Labels: newbie
>
> 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).
> Would be good for example, to keep track of whether Kafka Streams is
> starting/running/rebalancing
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
