Right. It is currently java integer. However, as per previous thread, it seems possible to change it to a string. In that case, we can use instance IDs, IP addresses, custom ID generators, etc. How are you currently generating broker IDs from IP address? Chef script or custom shell script?
On 1 October 2013 18:34, Maxime Brugidou <maxime.brugi...@gmail.com> wrote: > I think it currently is a java (signed) integer or maybe this was > zookeeper? > We are generating the id from IP address for now but this is not ideal (and > can cause integer overflow with java signed ints) > On Oct 1, 2013 12:52 PM, "Aniket Bhatnagar" <aniket.bhatna...@gmail.com> > wrote: > > > I would like to revive an older thread around auto generating broker ID. > As > > a AWS user, I would like Kafka to just use the instance's ID or > instance's > > IP or instance's internal domain (whichever is easier). This would mean I > > can easily clone from a AMI to launch kafka instances without having to > > worry about setting a unique broker ID. This also alows me to setup auto > > scaling. > > > > I realize 1 size may not fit all in this case. Other strategies that may > > work for other cloud providers are generate the UUID and persist it on a > > disk, etc. > > > > What I propose is a way to define a a broker ID generation strategy in > the > > configuration file which points to a class file that is responsible for > > generating the ID. Is this something being already worked upon? > > >
