You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by Kim Chew <kc...@gmail.com> on 2016/02/24 19:25:02 UTC
Fetching meta from Kafka continuously.
We have shut down some nodes from our cluster yesterday and now we are
seeing tons of these in the log,
2016-02-24 18:11:23 INFO SyncProducer:68 - Connected to
ip-172-30-198-64.us-west-2.compute.internal:9092 for producing
2016-02-24 18:11:23 INFO SyncProducer:68 - Disconnecting from
ip-172-30-198-64.us-west-2.compute.internal:9092
2016-02-24 18:11:23 INFO ConsumerFetcherManager:68 -
[ConsumerFetcherManager-1456295103918] Added fetcher for partitions
ArrayBuffer()
2016-02-24 18:11:23 INFO VerifiableProperties:68 - Verifying properties
2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property client.id is
overridden to utils_backup
2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property
metadata.broker.list is overridden to
ip-172-30-198-19.us-west-2.compute.internal:9092,ip-172-30-198-64.us-west-2.compute.internal:9092,ip-172-30-200-37.us-west-2.compute.internal:9092
2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property
request.timeout.ms is overridden to 30000
2016-02-24 18:11:23 INFO ClientUtils$:68 - Fetching metadata from broker
id:8,host:ip-172-30-198-64.us-west-2.compute.internal,port:9092 with
correlation id 189686 for 2 topic(s) Set(container, profile-data-2)
I am new to Kafka so although I know it has something to do with the
brokers, I would like to know what has happened and what is the best way to
fix it?
TIA
Re: Fetching meta from Kafka continuously.
Posted by Kim Chew <kc...@gmail.com>.
Problem solved. There was a DNS problem for one of the brokers.
Kim
On Mon, Feb 29, 2016 at 12:56 AM, Jens Rantil <je...@tink.se> wrote:
> Hi,
>
> Could it be that you need rebalance your topics, perhaps?
>
> Cheers,
> Jens
>
> On Wed, Feb 24, 2016 at 7:25 PM, Kim Chew <kc...@gmail.com> wrote:
>
> > We have shut down some nodes from our cluster yesterday and now we are
> > seeing tons of these in the log,
> >
> >
> > 2016-02-24 18:11:23 INFO SyncProducer:68 - Connected to
> > ip-172-30-198-64.us-west-2.compute.internal:9092 for producing
> > 2016-02-24 18:11:23 INFO SyncProducer:68 - Disconnecting from
> > ip-172-30-198-64.us-west-2.compute.internal:9092
> > 2016-02-24 18:11:23 INFO ConsumerFetcherManager:68 -
> > [ConsumerFetcherManager-1456295103918] Added fetcher for partitions
> > ArrayBuffer()
> > 2016-02-24 18:11:23 INFO VerifiableProperties:68 - Verifying properties
> > 2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property client.id
> is
> > overridden to utils_backup
> > 2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property
> > metadata.broker.list is overridden to
> >
> >
> ip-172-30-198-19.us-west-2.compute.internal:9092,ip-172-30-198-64.us-west-2.compute.internal:9092,ip-172-30-200-37.us-west-2.compute.internal:9092
> > 2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property
> > request.timeout.ms is overridden to 30000
> > 2016-02-24 18:11:23 INFO ClientUtils$:68 - Fetching metadata from broker
> > id:8,host:ip-172-30-198-64.us-west-2.compute.internal,port:9092 with
> > correlation id 189686 for 2 topic(s) Set(container, profile-data-2)
> >
> > I am new to Kafka so although I know it has something to do with the
> > brokers, I would like to know what has happened and what is the best way
> to
> > fix it?
> >
> > TIA
> >
>
>
>
> --
> Jens Rantil
> Backend engineer
> Tink AB
>
> Email: jens.rantil@tink.se
> Phone: +46 708 84 18 32
> Web: www.tink.se
>
> Facebook <https://www.facebook.com/#!/tink.se> Linkedin
> <
> http://www.linkedin.com/company/2735919?trk=vsrp_companies_res_photo&trkInfo=VSRPsearchId%3A1057023381369207406670%2CVSRPtargetId%3A2735919%2CVSRPcmpt%3Aprimary
> >
> Twitter <https://twitter.com/tink>
>
Re: Fetching meta from Kafka continuously.
Posted by Jens Rantil <je...@tink.se>.
Hi,
Could it be that you need rebalance your topics, perhaps?
Cheers,
Jens
On Wed, Feb 24, 2016 at 7:25 PM, Kim Chew <kc...@gmail.com> wrote:
> We have shut down some nodes from our cluster yesterday and now we are
> seeing tons of these in the log,
>
>
> 2016-02-24 18:11:23 INFO SyncProducer:68 - Connected to
> ip-172-30-198-64.us-west-2.compute.internal:9092 for producing
> 2016-02-24 18:11:23 INFO SyncProducer:68 - Disconnecting from
> ip-172-30-198-64.us-west-2.compute.internal:9092
> 2016-02-24 18:11:23 INFO ConsumerFetcherManager:68 -
> [ConsumerFetcherManager-1456295103918] Added fetcher for partitions
> ArrayBuffer()
> 2016-02-24 18:11:23 INFO VerifiableProperties:68 - Verifying properties
> 2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property client.id is
> overridden to utils_backup
> 2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property
> metadata.broker.list is overridden to
>
> ip-172-30-198-19.us-west-2.compute.internal:9092,ip-172-30-198-64.us-west-2.compute.internal:9092,ip-172-30-200-37.us-west-2.compute.internal:9092
> 2016-02-24 18:11:23 INFO VerifiableProperties:68 - Property
> request.timeout.ms is overridden to 30000
> 2016-02-24 18:11:23 INFO ClientUtils$:68 - Fetching metadata from broker
> id:8,host:ip-172-30-198-64.us-west-2.compute.internal,port:9092 with
> correlation id 189686 for 2 topic(s) Set(container, profile-data-2)
>
> I am new to Kafka so although I know it has something to do with the
> brokers, I would like to know what has happened and what is the best way to
> fix it?
>
> TIA
>
--
Jens Rantil
Backend engineer
Tink AB
Email: jens.rantil@tink.se
Phone: +46 708 84 18 32
Web: www.tink.se
Facebook <https://www.facebook.com/#!/tink.se> Linkedin
<http://www.linkedin.com/company/2735919?trk=vsrp_companies_res_photo&trkInfo=VSRPsearchId%3A1057023381369207406670%2CVSRPtargetId%3A2735919%2CVSRPcmpt%3Aprimary>
Twitter <https://twitter.com/tink>