kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jacot <dja...@confluent.io>
Subject Re: Multiple bootstrap clusters in kafka producer config
Date Wed, 21 Aug 2019 07:28:11 GMT
Hello,

As of today, the producer is able to talk to only one Kafka cluster.
*bootstrap.servers* is to provide a list of brokers belonging to the same
cluster to ensure at least one is available.

In your case, you have to replicate the data from the first cluster to the
second cluster with mirror maker for instance.

Best,
David

On Mon, Aug 12, 2019 at 11:13 AM lsroudi abdel <lsroudi@gmail.com> wrote:

> I guess it more about replication, you can push your data in one choosen
> cluster and replicate your data to the second one by using mirror maker or
> confluent replicator or the new open sourced project by LinkedIn,
> "Brooklin"
>
> Le lun. 12 août 2019 à 10:19, Garvit Sharma <eng.garvit@gmail.com> a
> écrit :
>
> > Thanks, Isroudi. But in my usecase there are two separate zookeeper as
> > well. Let me know how would it handle.
> >
> > On Mon, Aug 12, 2019 at 1:45 PM lsroudi abdel <lsroudi@gmail.com> wrote:
> >
> > > If it is two cluster it mean you have two zookeeper, I guess you can't
> do
> > > that, I f you have one zookeeper it will be ok, in the case you have
> one
> > > zookeeper it's just an architecture with replica across two data
> center,
> > I
> > > hope it clear for you
> > >
> > > Le lun. 12 août 2019 à 09:22, Garvit Sharma <eng.garvit@gmail.com>
a
> > > écrit :
> > >
> > > > Hi,
> > > >
> > > > I have 2 kafka clusters in different data-centers so can I provide
> the
> > > dns
> > > > hostnames of both the clusters separated by comma in
> > *bootstrap.servers*
> > > > key in producer config ?
> > > >
> > > > If I provide two different clusters in *bootstrap.servers *then how
> > would
> > > > the events get published ?
> > > > Would events get published to both the clusters or either of them
> > > randomly
> > > > ?
> > > >
> > > > Looking forward to hearing from you.
> > > >
> > > > Thanks
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message