Re: restart Kafka Streams application takes around 5 minutes

Hi Guozhang, I am using 0.10.2.0. Will try the trunk and report back. Thanks Tianji On Wed, Mar 15, 2017 at 5:25 PM, Guozhang Wang wrote: > Are you building with any released versions of Kafka or with a build from > Kafka trunk? There are a few fixes we have made post 0.10.2 in trunk that > ha

Re: Kafka Stream: RocksDBKeyValueStoreSupplier performance

Hi Eno, Thanks for your help. Very appreciated. Thanks Tianji On Wed, Mar 15, 2017 at 4:29 PM, Eno Thereska wrote: > Tianji, > > A couple of things: > > - for now could you use RocksDb without the cache? I've opened a JIRA to > verify why it's slower with the cache: https://issues.apache.org/

Re: performance regression with 0.10.2.0 client talking to 0.10.0.1 servers

Hi Alex, The following could be the reason for your performance issue: https://github.com/apache/kafka/pull/2694 Ismael On Thu, Mar 9, 2017 at 8:33 AM, Ismael Juma wrote: > Hi Alex, > > Yes, please file a JIRA and include as much detail as possible: configs > used by the broker and producer/c

Re: performance regression with 0.10.2.0 client talking to 0.10.0.1 servers

Sorry, after a second look, that PR only fixes a cosmetic issue, it shouldn't be the reason for the performance issue you are seeing. Ismael On Thu, Mar 16, 2017 at 12:57 PM, Ismael Juma wrote: > Hi Alex, > > The following could be the reason for your performance issue: > > https://github.com/a

Re: Need kafka client v0.9.0.2 / fix for KAFKA-3594

We haven't released v0.9.0.2. You can build client libraries from 0.9.0 branch. https://github.com/apache/kafka/tree/0.9.0 On Thu, Mar 16, 2017 at 3:21 AM, Phil Adams wrote: > I'm currently using the kafka-clients v0.9.0.1 library along with the > v0.9.0.1 kafka broker. > Unfortunately, we've ru

Re: Need kafka client v0.9.0.2 / fix for KAFKA-3594

I was just able to get the 0.9.0 source and build it right before seeing your email. Thanks for confirming what I did :) On Thu, Mar 16, 2017 at 9:31 AM, Manikumar wrote: > We haven't released v0.9.0.2. You can build client libraries from 0.9.0 > branch. > https://github.com/apache/kafka/tree/0

Re: Kafka Streams: ReadOnlyKeyValueStore range behavior

Hi Matthias. Thank you for your response. Yes, I was able to reproduce the null issue reliably. I can't open a JIRA at this time, but I can say I was using 0.10.1.0 and it was trivial to reproduce. Just send records and the tombstones to a table topic. Then scan the range. You'll see the tombstone

Re: Kafka Streams: ReadOnlyKeyValueStore range behavior

Can you check if the problem exist for 0.10.2, too? (0.10.2 is compatible to 0.10.1 broker -- so you can upgrade your Streams code independently from the brokers). About the range: I did double check this, and I guess my last answer was not correct, and range() should return ordered data, but I go

Re: Kafka Streams: ReadOnlyKeyValueStore range behavior

I think what you are seeing is that the order is not guaranteed across partitions. When you use Queryable State you are actually querying multiple underlying stores, i.e., one per partition. The implementation iterates over one store/partition at a time, so the ordering will appear random. This cou

Kafka Streams: lockException

Hi there, I always got this crashes and wonder if anyone knows why. Please let me know what information I should provide to help with trouble shooting. I am using 0.10.2.0. My application is reading one topic and then groupBy().aggregate() 50 times on different keys. I use memory store, without

Re: Kafka Streams: lockException

Hi Tianji, How many threads does your app use? One reason is explained here: https://groups.google.com/forum/#!topic/confluent-platform/wgCSuwIJo5g , you might want to increase max.poll.interval config value. If that does

Re: How does offsets.retention.minutes work

Yes, that is correct. I filed a JIRA about that issue here: https://issues.apache.org/jira/browse/KAFKA-4682 -James > On Mar 15, 2017, at 8:51 PM, tao xiao wrote: > > Hi team, > > I know that Kafka deletes offset for a consumer group after a period of > time (configured by offsets.retention.m