More specifically, see: https://github.com/mesos/kafka#failed-broker-recovery
On Wed, May 25, 2016 at 6:02 PM, craig w <codecr...@gmail.com> wrote: > The Kafka framework can be used to deploy brokers. It will also bring a > broker back up on the server it was last running on (within a certain > amount of time). > > However the Kafka framework doesn't run brokers in containers. > > > On Wednesday, May 25, 2016, Radoslaw Gruchalski <ra...@gruchalski.com> > wrote: > >> Kiran, >> >> If you’re using Docker, you can use Docker on Mesos, you can use >> constraints to force relaunched kafka broker to always relaunch at the same >> agent and you can use Docker volumes to persist the data. >> Not sure if https://github.com/mesos/kafka provides these capabilites. >> – >> Best regards, >> Radek Gruchalski >> ra...@gruchalski.com >> de.linkedin.com/in/radgruchalski >> >> Confidentiality: >> This communication is intended for the above-named person and may be >> confidential and/or legally privileged. >> If it has come to you in error you must take no action based on it, nor >> must you copy or show it to anyone; please delete/destroy and inform the >> sender immediately. >> >> On May 25, 2016 at 10:58:06 PM, Karnam, Kiran (kkar...@ea.com) wrote: >> >> Hi All, >> >> We are using Docker containers to deploy Kafka, we are planning to use >> mesos for the deployment and maintenance of containers. Is there a way >> during upgrade that we can persist the data so that it is available for the >> upgraded container. >> >> we don't want the clusters to go into chaos with data replicating around >> the network because a node that was upgraded suddenly has no data >> >> Thanks, >> Kiran >> > > > -- > > https://github.com/mindscratch > https://www.google.com/+CraigWickesser > https://twitter.com/mind_scratch > https://twitter.com/craig_links > > > -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links
