Matthias,
We moved to streams client 1.0.0 with 0.10.2.x broker now. Haven't see this
issue ever since.
Thanks!
Srikanth
On Thu, Dec 7, 2017 at 12:15 AM, Matthias J. Sax
wrote:
> Running Streams 1.0.0 should just work with 0.10.2 brokers. Of course,
> you can't use EOS feature.
>
> Not sure ho
Running Streams 1.0.0 should just work with 0.10.2 brokers. Of course,
you can't use EOS feature.
Not sure how your app got into this bad state. But if is does not
recover from it, delete the store directory seems to be reasonable --
also for stateful application, you won't loose data, as we recre
I will take the rebound of this subject to post a question if that's ok.
What is the best solution between start X instances with
num_stream_thread=1 to one instance with X threads, knowing that I have
only 2 dedicated servers at my disposal ?
The best should be to have more hosts but currently we
Thanks Matthias. Please find my response inline.
On Wed, Dec 6, 2017 at 12:34 AM, Matthias J. Sax
wrote:
> Hard to say.
>
> However, deleting state directories will not have any negative impact as
> you don't use stores. Thus, why do you not want to do this?
> We are running this in a prod-like
Hard to say.
However, deleting state directories will not have any negative impact as
you don't use stores. Thus, why do you not want to do this?
Another workaround you can do, it to start four applications with 1
thread each -- this would isolate the instances further and avoid the
lock issue (y
Hello,
We noticed that a kafka streams app is stuck in rebalance state with below
error.
Two instance of the app were running fine until a rebalace was
triggered(possibly due to network issue).
Both app instance are running(no app restart)
App itself doesn't create/use state store. NUM_STREAM_THRE
