Not sure if this helps, but I also just tried adding this line immediately 
before I call my send() code:
p.partitionsFor("lowercaseStrings")
where p is my KafkaProducer and lowercaseStrings is my topic.  
partitionsFor() returned immediately and successfully with expected values for 
partition information.  Not 100% sure but from the KafkaProducer code it 
appears this pulls information from metadata, so if that's true I do have a 
meaningful connection to my server and getting the metadata.

      From: Greg Zoller <gwzol...@yahoo.com.INVALID>
 To: "users@kafka.apache.org" <users@kafka.apache.org> 
 Sent: Saturday, April 16, 2016 3:02 PM
 Subject: Re: Producer Bug? Moving form 0.9.0.1 to 0.10.1.0-SNAPSHOT (latest)
   
Hi, Ismael,
Thank you for your help! 
The only difference in usage between the versions is that I flip my project 
dependency version from 0.9.0.1 to 0.10.1.0 and clean+test.  Code is identical, 
including the Docker packaging.  
OK, so I'm looking at the logs and honestly I'm not 100% sure what I'm looking 
at.  I didn't see anything that looked like an error but that doesn't mean its 
not there.
I'd be very grateful if you'd be willing to look.  I've attached the compressed 
logs for just this one failed test and no more, so they're small. (attached)
Greg

      From: Ismael Juma <isma...@gmail.com>
 To: users@kafka.apache.org 
 Sent: Saturday, April 16, 2016 2:30 PM
 Subject: Re: Producer Bug? Moving form 0.9.0.1 to 0.10.1.0-SNAPSHOT (latest)
  
Hi Greg,

I asked if there were any errors in the broker logs because the metadata
request sent by the producer timed out. No messages can be sent if the
producer is unable to retrieve the topic metadata. If the broker has
started without errors, then the producer is unable to reach it for some
reason (network setup or config problem are common reasons).

I know you said this works for 0.9.0.1, but are you sure there are is no
other difference apart from the version? It may be worth trying it without
using Docker.

Ismael
0.10.1.0-SNAPSHOT is the broker too

My procedure is the same as 0.9.0.1.  I do a signed tgz build and then a
local maven install.  I unpack the tgz into a docker just like
spotify/kafka.  I run that as my server broker with ports 9092 and 2181
exposed.

I link my producer code in the gist to my local maven snapshot lib (not in
a Docker)

Same process works for the 0.9 version

Sent from my iPhone

> On Apr 15, 2016, at 7:17 PM, Ismael Juma <ism...@juma.me.uk> wrote:
>
> Hi Greg,
>
> What is the broker version? Have you checked that there are no errors
> logged in the broker?
>
> Ismael
>
> On Fri, Apr 15, 2016 at 11:55 PM, Greg Zoller <gwzol...@yahoo.com.invalid>
> wrote:
>
>> ok... one more attempt for a working link...
>> https://gist.github.com/gzoller/145faef1fefc8acea212e87e06fc86e8
>> (If this doesn't work please copy/paste link.)
>>
>>      From: Greg Zoller <gwzol...@yahoo.com>
>> To: "users@kafka.apache.org" <users@kafka.apache.org>; Greg Zoller <
>> gwzol...@yahoo.com>
>> Sent: Friday, April 15, 2016 5:53 PM
>> Subject: Re: Producer Bug? Moving form 0.9.0.1 to 0.10.1.0-SNAPSHOT
>> (latest)
>>
>> GIST: https://gist.github.com/gzoller/145faef1fefc8acea212e87e06fc86e8
>>
>>      From: Greg Zoller <gwzol...@yahoo.com.INVALID>
>> To: "users@kafka.apache.org" <users@kafka.apache.org>
>> Sent: Friday, April 15, 2016 5:51 PM
>> Subject: Producer Bug? Moving form 0.9.0.1 to 0.10.1.0-SNAPSHOT (latest)
>>
>> I have built 0.10.1.0-SNAPSHOT from scratch and used it with
>> my KafkaProducer code from 0.9.0.1.It compiled just fine but when run it
>> hangs (times out actually) on send().  I've created a gist below with a
>> clip from the output in comments at the end of the file.
>> Remember, this code worked flawlessly as-is with 0.9.0.1.  Did a breaking
>> change occur that requires this code to be modified, or is this a bug in
>> 0.10.1.0-SNAPSHOT?
>> Kafka populate topic
>>
>>
>> |
>> |
>> |
>> |  |    |
>>
>>  |
>>
>>  |
>> |
>> |    |
>> Kafka populate topic
>> Kafka populate topic  |  |
>>
>>  |
>>
>>  |
>>
>>
>>
>>
>>
>>
>>


   

  

Reply via email to