Mesos supports persistent volumes and what they call "dynamic reservations", which this framework supports. If the application is killed, and the host is still up, it will be restarted on the same host and re-attached to the volume which has the data, otherwise, kafka will just replicate to the new broker (as it does).
The initial code for adding the dynamic reservation bits was added last November as it is a relatively new feature in Mesos:
https://github.com/mesos/kafka
Mesos supports persistent volumes and what they call "dynamic reservations", which this framework supports. If the application is killed, and the host is still up, it will be restarted on the same host and re-attached to the volume which has the data, otherwise, kafka will just replicate to the new broker (as it does).
The initial code for adding the dynamic reservation bits was added last November as it is a relatively new feature in Mesos:
https://github.com/mesos/kafka/commit/455b20f94b9166b026ea