Re: Kafka Streams : CommitFailedException

2017-11-08 Thread Tony John
Hello Guozhang, Thanks for the analysis. Figured out the reason for the OOM and it was actually caused by an in memory queue in the app itself. I have fixed it and right now it all looks good. Sorry for the inconvenience and thanks for helping out. Thanks, Tony On Wed, Nov 8, 2017 at 1:20 AM,

Re: Kafka Streams : CommitFailedException

2017-11-07 Thread Guozhang Wang
Hello Tony, You mentioned in 0.11.0.0 the props.put(StreamsConfig.NUM_STREAM_THREADS_CONFIG, 1) while in 0.11.0.1 props.put(StreamsConfig.NUM_STREAM_THREADS_CONFIG, 2). But from your logs it seems you set this config as 2 in both versions. Right? Anyways, I took a look into your logs and I think

Re: Kafka Streams : CommitFailedException

2017-11-07 Thread Tony John
Hi Guozang, Thanks for looking into this. I was using 0.11.0.0 version of the library earlier when I was getting the CommitFailed exception and the tasks were terminating. The application config then was Replication Factor = 2, Num Stream Threads = 1, Consumer Max Poll Records = 1000 & Consumer

Re: Kafka Streams : CommitFailedException

2017-11-03 Thread Guozhang Wang
Hello Tony, Which version of Kafka did you use for the Streams library? And could you share your settings (num. threads in total, num of tasks etc) and your exception stack trace so that we can help you better identifying the root cause of the exception? Guozhang On Thu, Nov 2, 2017 at 4:09

Kafka Streams : CommitFailedException

2017-11-02 Thread Tony John
Hi All, I am facing CommitFailedException in my streams application. As per the log I tried changing the max.poll.interval.ms and max.poll.records. But both didn't help. PFA the full stack trace of the exception and below is the streams configuration used. What else could be wrong? val props =