Can you clarify what is meant by using the ELB as a metadata broker? Let's say I have a python script that sends messages into kafka. Do I have to provide a list of brokers or can I use the ELB DNS alias that will round-robin to all my healthy brokers? Much easier to use the ELB instead of hard-coding server names or IPs. And when the broker list expands or shrinks, I have to them edit my python code?
Thanks for any help. On Sun, May 3, 2015 at 11:05 AM, Jiangjie Qin <[email protected]> wrote: > Yes. > > On 5/3/15, 10:57 AM, "Chandrashekhar Kotekar" <[email protected]> > wrote: > > >Thanks a lot for the information. So basically each broker needs to have > >his own public IP address? > > > > > >Regards, > >Chandrash3khar Kotekar > >Mobile - +91 8600011455 > > > >On Sun, May 3, 2015 at 11:09 PM, Jiangjie Qin <[email protected]> > >wrote: > > > >> You can use ELB address as metadata broker list. But you still need to > >> allow direct traffic from clients to a brokers because clients need to > >> talk to a specific broker who has the interested partition. > >> > >> Jiangjie (Becket) Qin > >> > >> On 5/2/15, 11:10 AM, "Chandrashekhar Kotekar" > >><[email protected]> > >> wrote: > >> > >> >Hi, > >> > > >> >I am new to Apache Kafka. I have played with it on my laptop. > >> > > >> >I want to use Kafka in AWS. Currently we have tomcat web servers based > >> >REST > >> >API. We want to replace REST API with Apache Kafka, web servers are > >>behind > >> >ELB. > >> > > >> >I would like to know if we can keep Kafka brokers behind ELB? Will it > >> >work? > >> > > >> >Regards, > >> >Chandrash3khar Kotekar > >> >Mobile - +91 8600011455 > >> > >> > >
