Thanks Sameer.
Please stay tuned as we work on back port it to 0.10.2.1.
Guozhang
On Fri, Jul 28, 2017 at 10:15 PM, Sameer Kumar
wrote:
> Hi Guozhang,
>
> I am using 10.2.1.
>
> -Sameer.
>
> On Sat, Jul 29, 2017 at 12:05 AM, Guozhang Wang
> wrote:
Hi Guozhang,
I am using 10.2.1.
-Sameer.
On Sat, Jul 29, 2017 at 12:05 AM, Guozhang Wang wrote:
> Sameer,
>
> This bug should be already fixed in trunk.
>
> Which version of Kafka Streams are you running with? We can consider
> backport it and have a bug-fix release if it
Sameer,
This bug should be already fixed in trunk.
Which version of Kafka Streams are you running with? We can consider
backport it and have a bug-fix release if it turns out to be a common issue.
Guozhang
On Fri, Jul 28, 2017 at 4:57 AM, Damian Guy wrote:
> It is due
It is due to a bug. You should set
StreamsConfig.STATE_DIR_CLEANUP_DELAY_MS_CONFIG to Long.MAX_VALUE - i.e.,
disabling it.
On Fri, 28 Jul 2017 at 10:38 Sameer Kumar wrote:
> Hi,
>
> I am facing this error, no clue why this occurred. No other exception in
> stacktrace was
Hi,
I am facing this error, no clue why this occurred. No other exception in
stacktrace was found.
Only thing different I did was I ran kafka streams jar on machine2 a couple
of mins after i ran it on machine1.
Please search for this string in the log below:-