Yes, I don't think they need to be sequential though we always assign them sequentially at LinkedIn.
-Jay On Fri, Dec 9, 2011 at 9:46 AM, Florian Leibert <f...@leibert.de> wrote: > But this means that I can pick one at random - it doesn't have to be > sequential as long as it's the same after restart? > > 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 > > > > > > > > > -- > Best regards, > > Florian > http://twitter.com/flo <http://twitter.com/floleibert> > http://flori.posterous.com/ >
