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
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
> occasionally prevents mul
Dear All,
The error seems to be NOT_COORDINATOR_FOR_GROUP.
The exception thrown in
org.apache.kafka.clients.consumer.internals.RequestFuture is:
org.apache.kafka.common.errors.NotCoordinatorForGroupException: This is
not the correct coordinator for this group.
How
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,
> The error seems to be NOT_CO
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 roo
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
(org.apache.kafka.common.netw
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)
> I get same exception. Wh
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 kafka
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.
One
