Sure, I will attach next time. Thanks for your help.
-Sameer.
On Wed, Aug 9, 2017 at 3:27 PM, Damian Guy wrote:
> Hi,
>
> This is a bug in 0.11. You can work around it by setting
> StreamsConfig.STATE_DIR_CLEANUP_DELAY_MS_CONFIG to Long.MAX_VALUE
>
> Also, if you have logs it would be easier to
The issue was fixed by this:
https://issues.apache.org/jira/browse/KAFKA-5562 it is on trunk, but will
likely be back ported to 0.11
On Wed, 9 Aug 2017 at 10:57 Damian Guy wrote:
> Hi,
>
> This is a bug in 0.11. You can work around it by setting
> StreamsConfig.STATE_DIR_CLEANUP_DELAY_MS_CONFIG
Hi,
This is a bug in 0.11. You can work around it by setting
StreamsConfig.STATE_DIR_CLEANUP_DELAY_MS_CONFIG to Long.MAX_VALUE
Also, if you have logs it would be easier to either attach them or put them
in a gist. It is a bit hard to read in an email.
Thanks,
Damian
On Wed, 9 Aug 2017 at 10:10
Hi All,
I wrote a Kafka Streams job that went running for 3-4 hrs, after which it
started throwing these errors.Not sure why we got these errors.
I am using Kafka 11.0 both on broker side as well as on consumer side.
*Machine1*
2017-08-08 17:25:35 INFO StreamThread:193 - stream-thread
[LICSp-7
