Thank you for pointing me to that JIRA. It indeed is the same issue we
discussed in this thread. I'll keep a watch on that JIRA for the code to
be merged.
-Jaikiran
On Thursday 02 March 2017 07:11 PM, Rajini Sivaram wrote:
This issue is being addressed in KAFKA-4631. See
https://issues.apache
This issue is being addressed in KAFKA-4631. See
https://issues.apache.org/jira/browse/KAFKA-4631 and the discussion in the
PR https://github.com/apache/kafka/pull/2622 for details.
Regards,
Rajini
On Thu, Mar 2, 2017 at 4:35 AM, Jaikiran Pai
wrote:
> For future reference - I asked this questi
Jaikiran,
What about
1) create topic
2) create consumer1 and do consumer1.partitionsFor() until it succeeds
3) close consumer1
4) create consumer2 and do consumer2.subscribe()
-James
An update on this. This workaround has worked out fine and our initial
tests so far show that it gets us pas
Yes, that was going to be my last resort attempt :) I'm going to give that
a try today and see how it goes. Although it isn't that great of a
solution, I don't mind doing it since the logic resides at one single place
in our application.
-Jaikiran
On Tuesday, February 28, 2017, James Cheng wrote
> On Feb 26, 2017, at 10:36 PM, Jaikiran Pai wrote:
>
> An update on one of the workaround I tried - I added some logic in our
> consumption part to wait for the KafkaConsumer.partitionsFor() to return the
> topic name in the list, before actually considering the KafkaConsumer ready
> to con
An update on one of the workaround I tried - I added some logic in our
consumption part to wait for the KafkaConsumer.partitionsFor() to return
the topic name in the list, before actually considering the
KafkaConsumer ready to consume/poll the messages. Something like
this[1]. This does success
James, thank you very much for this explanation and I now understand the
situation much more clearly. I wasn't aware that the consumer's
metadata.max.age.ms could play a role in this. I was under the
impression that the 5 minute timeout is some broker level config which
was triggering this cons
> On Feb 23, 2017, at 10:03 PM, Jaikiran Pai wrote:
>
> (Re)posting this from the user mailing list to dev mailing list, hoping for
> some inputs from the Kafka dev team:
>
> We are on Kafka 0.10.0.1 (server and client) and use Java consumer/producer
> APIs. We have an application where we cr
(Re)posting this from the user mailing list to dev mailing list, hoping
for some inputs from the Kafka dev team:
We are on Kafka 0.10.0.1 (server and client) and use Java
consumer/producer APIs. We have an application where we create Kafka
topics dynamically (using the AdminUtils Java API) and
