Re: Kafka Streams: context.forward() with downstream name

Thanks Yuto for your code snippet. Since you need to access a customized external storage for metadata, that indeed cannot be wrapped in any built-in operators in the Streams DSL yet, and your code example in the previous email would be close to the best you can do with the high-level DSL now.

Cleaning up a topic that has had its metadata deleted

Hello, I have a problem with my Kafka cluster (0.8.2) where there's a topic that has had its partition metadata deleted from /brokers/topics/exampleTopic/partitions in Zookeeper. I think this confused the brokers and caused them to end up in a state where I'm unable to delete the topic using

Re: New consumer API waits indefinitely

This is the same logs i get with my local kafka server, that works fine.. On 5 April 2016 at 10:20, Ratha v wrote: > HI Niko; > I face this issue with linux systems.. > I changed the logging level to debug and when I start and stop my consumer > (stopping the program) >

Re: New consumer API waits indefinitely

HI Niko; I face this issue with linux systems.. I changed the logging level to debug and when I start and stop my consumer (stopping the program) I get same exception. What is the cause here? [2016-04-05 00:01:08,784] DEBUG Connection with /192.xx.xx.248 disconnected

RE: New consumer API waits indefinitely

M. Lohith Samaga, Your Java code looks fine. Usually, if consumer.poll(100); doesn't return, there is probably a basic connection error. If Kafka can't connect, it will internally go into an infinite loop. To me, that doesn't seem like a good design, but that's a separate tangent. Turn SLF4J

Re: New consumer API waits indefinitely

Hi Lohith, Are there any errors in your broker logs? I think there may be some issues with compacted topics on Windows and the new consumer uses a compacted topic to store offsets. Ismael On Mon, Apr 4, 2016 at 12:20 PM, Lohith Samaga M wrote: > Dear All, >

Re: (auto.commit.interval = heartbeat.interval) => infinite rebalance loop

Yes, it seems that it can be something related to that. Well, glad that someone already mapped it. Waiting for the fix and see if the solves my issue. On 31 March 2016 at 20:49, Jason Gustafson wrote: > This could be caused by a bug in our client's network layer which >

RE: New consumer API waits indefinitely

Thanks Ratha. I am trying tounderstand the code... Best regards / Mit freundlichen Grüßen / Sincères salutations M. Lohith Samaga -Original Message- From: Ratha v [mailto:vijayara...@gmail.com] Sent: Monday, April 04, 2016 12.22 To: users@kafka.apache.org Subject: Re: New consumer API

Re: New consumer API waits indefinitely

Still struggling :) Check following threads; - If my producer producing, then why the consumer couldn't consume? it stuck @ poll() - Consumer thread is waiting forever, not returning any objects I think new APIs are recommended. On 4 April 2016 at 16:37, Lohith Samaga M

RE: New consumer API waits indefinitely

Thanks for letting me know. Is there any work around? A fix? Which set of API is recommended for production use? Best regards / Mit freundlichen Grüßen / Sincères salutations M. Lohith Samaga -Original Message- From: Ratha v [mailto:vijayara...@gmail.com] Sent: Monday, April 04,

Re: If my producer producing, then why the consumer couldn't consume? it stuck @ poll()

when I list down the partition info ; List info = consumer.partitionsFor(topic); it returns info like; [Partition(topic = *MY_TOPIC*, partition = 0, leader = 1012, replicas = [1012,], isr = [1012,]] My communication with the broker looks like fine. I see more than 1000 messages for the topic