Florian, >> When using Zookeeper, couldn't ZK just give each broker if registered as a SEQ node a generated ID that's guaranteed to be unique? Otherwise can this ID be a randomly generated ID?
If you do that, then what happens when you merely bounce the broker ? It might end up getting a different id each time, which will break consumer logic. The purpose of a unique broker id is to be able to identify a Kafka broker, without having to know its host-name/IP. This allows you to switch the machine hosting a broker, without changing any client config. Thanks, Neha On Fri, Dec 9, 2011 at 9:37 AM, Jun Rao <jun...@gmail.com> wrote: > Florian, > > The broker id uniquely identifies a broker. Every time a broker is > restarted, we want the broker to come up with the same id. The consumer > relies on the broker id to resume consumption properly. > > Thanks, > > Jun > > On Fri, Dec 9, 2011 at 8:34 AM, Florian Leibert <f...@leibert.de> wrote: > > > Hi - > > I see there's a static broker-id in the properties files. Is this > optional? > > When using Zookeeper, couldn't ZK just give each broker if registered as > a > > SEQ node a generated ID that's guaranteed to be unique? Otherwise can > this > > ID be a randomly generated ID? Basically I'd like to bring up instances > in > > EC2 without having to worry about the state of other brokers... > > > > Thanks! > > Flo > > >
