Hey Stevo, "can be elastically and transparently expanded without downtime." is the goal of Kafka on Mesos https://github.com/mesos/kafka as Kafka as the ability (knobs/levers) to-do this but has to be made to-do this out of the box.
e.g. in Kafka on Mesos when a broker fails, after the configurable max fail over timeout (meaning it is truly deemed hard failure) then a broker (with the same id) will automatically be started on a another machine, data replicated and back in action once that is done, automatically. Lots more features already in there... we are also in progress to auto balance partitions when increasing/decreasing the size of the cluster and some more goodies too. ~ Joe Stein - - - - - - - - - - - - - - - - - http://www.stealth.ly - - - - - - - - - - - - - - - - - On Fri, Mar 13, 2015 at 8:43 AM, Stevo Slavić <ssla...@gmail.com> wrote: > Hello Apache Kafka community, > > On Apache Kafka website home page http://kafka.apache.org/ it is stated > that Kafka "can be elastically and transparently expanded without > downtime." > Is that really true? More specifically, can one just add one more broker, > have another partition added for the topic, have new broker assigned to be > the leader for new partition, have producers correctly write to the new > partition, and consumers read from it, with no broker, consumer or producer > downtime, no data loss, no manual action to move data from existing > partitions to new partition? > > Kind regards, > Stevo Slavic. >
