+1
Started using kafka client 0.10.2.1 for our streams applications, seen a
much greater improvement on retries when failures occur.
We've been running without manual intervention for > 24 hours which is
something we haven't seen in awhile.
Found it odd that the RC tag wasn't within the version o
Hi Matthias and Guozhang,
+1 (non-binding)
We eventually solved this on our end. It boiled down to dodgy data and
unexpected hidden errors in our processing steps. This eventually resulted
in a session time out which triggered the rebalances.
Thanks again for all your help.
Ian.
On 14 February
Hi Guozhang,
Thank you for your assistance on this.
> About the stack trace pasted before: is it tailing some warning logs like
"Could not create task ... Will retry"
Yes, we see the following:
17/02/13 21:49:55 WARN internals.StreamThread: Could not create task 0_93.
Will retry.
org.apache.kaf
thing you can try out is to delete the local app state
> directory. This will give you a clean restart -- on the cost of state
> recreation (for the first start only). Afterward stop and restart you
> app to see if the issue is resolved.
>
>
> Right now, I canno
Seeing the following failure when using multi-threaded streams
Feb 10 17:21:15 ip-172-31-137-57 docker/43e65fe123cd[826]:
org.apache.kafka.streams.errors.LockException: task [0_21] Failed to lock
the state directory: /tmp/kafka-streams/text_pipeline_id/0_21
Feb 10 17:21:15 ip-172-31-137-57 docker/
