To: users@kafka.apache.org
Subject: Re: Metadata Request Loop?
I'm going to try both of these ideas.
Thank you so much Phil for speaking up. I thought I was the only one with this
issue. Your analysis was great. I think I can easily send a test message but
would I need to send one every 5
> publish a message within the first 5 minutes then I also saw a metadata
>> request every 100ms.
>>
>> Regards,
>> Phil Luckhurst
>>
>> -Original Message-
>> From: Fumo, Vincent [mailto:vincent_f...@cable.comcast.com]
>> Sent: 27 Apri
s,
> Phil Luckhurst
>
> -Original Message-
> From: Fumo, Vincent [mailto:vincent_f...@cable.comcast.com]
> Sent: 27 April 2016 20:48
> To: users@kafka.apache.org
> Subject: Re: Metadata Request Loop?
>
> client/producer : 0.9.0.1
> server/broker : 0.9.0.0
>
publish
a message within the first 5 minutes then I also saw a metadata request every
100ms.
Regards,
Phil Luckhurst
-Original Message-
From: Fumo, Vincent [mailto:vincent_f...@cable.comcast.com]
Sent: 27 April 2016 20:48
To: users@kafka.apache.org
Subject: Re: Metadata Request Loo
client/producer : 0.9.0.1
server/broker : 0.9.0.0
> On Apr 26, 2016, at 10:05 PM, Sharma Vinay wrote:
>
> What versions of kafka and client API are you using now?
> On Apr 26, 2016 3:35 PM, "Fumo, Vincent"
> wrote:
>
>> I spoke too soon. It's back doing the same thing.. which is really odd.
>>
What versions of kafka and client API are you using now?
On Apr 26, 2016 3:35 PM, "Fumo, Vincent"
wrote:
> I spoke too soon. It's back doing the same thing.. which is really odd.
>
> > On Apr 26, 2016, at 12:24 PM, Fumo, Vincent <
> vincent_f...@cable.comcast.com> wrote:
> >
> > Hello. I found th
I spoke too soon. It's back doing the same thing.. which is really odd.
> On Apr 26, 2016, at 12:24 PM, Fumo, Vincent
> wrote:
>
> Hello. I found the issue. The Ops team deployed kafka 0.8.1 and all my code
> was 0.9.0. Simple mistake and one that I should have thought of sooner. Once
> I ha
Hello. I found the issue. The Ops team deployed kafka 0.8.1 and all my code was
0.9.0. Simple mistake and one that I should have thought of sooner. Once I had
them bump up to the latest kafka all was well. Thank you for your help!
v
> On Apr 25, 2016, at 2:54 PM, vinay sharma wrote:
>
> Hi,
Hi,
Your code looks good. i don't see any reason there for frequent meta data
fetch but i will run it to verify.
I was able to replicate this issue with my consumer today where I killed 2
brokers out or 3 and ran consumer. I saw a lot of meta data requests in
wait for new leader for partitions fo
My code is very straightforward. I create a producer, and then call it to send
messages. Here is the factory method::
public Producer createProducer() {
Properties props = new Properties();
props.put("bootstrap.servers", "cmp-arch-kafka-01d.cc.com:9092");
props.put("key.serializer
2 producer's to same topic should not be a problem. There can be multiple
producers and consumers of same kafka topic.
I am not sure what can be wrong here. I can this at my end If you can share
producer code and any config of topic ot broker that you changed and is not
default.
Please also check
Hi. I've not set that value. My producer properties are as follows :
acks=all
retries=0
bath.size=1638
linger.ms=1
buffer.memory=33554432
compression.type=gzip
client.id=sds-merdevl
I have this running on two hosts with the same config. I thought that having
the same client.id on each would just
Generally a proactive metadata refresh request is sent by producer and
consumer every 5 minutes but this interval can be overriden with property "
metadata.max.age.ms" which has default value 30 i.e 5 minutes. Check if
you have set this property very low in your producer?
On Fri, Apr 22, 2016
13 matches
Mail list logo
