So far the Kafka framework has worked well in production. We launch the framework using marathon, then execute a few command line statements to add and start the brokers. On Oct 12, 2015 1:38 PM, "Dick Davies" <[email protected]> wrote:
> Hi Chris > > <personal opinion ahoy> > > Spark is a Mesos native, I'd have no hesitation running it on Mesos. > > Cassandra not so much - > that's not to disparage the work people are putting in there, I think > it's really interesting. But personally with complex beasts like Cassandra > I want to be running as 'stock' as possible, as it makes it easier to learn > from other peoples experiences. > > On 12 October 2015 at 17:47, Chris Elsmore < > [email protected]> wrote: > >> Hi all, >> >> Have just got back from a brilliant MesosCon Europe in Dublin, I learnt a >> huge amount and a big thank-you for putting on a great conference to all >> involved! >> >> >> I am looking to deploy a small (maybe 5 max) Cassandra & Spark cluster to >> do some data analysis at my current employer, and am a little unsure of the >> current status of the frameworks this would need to run on Mesos- both the >> mesosphere docs (which I’m guessing use the frameworks of the same name >> hosted on Github) and the Github ReadMes mention that these are not >> production ready, and the rough timeline of Q1 2016. >> >> I’m just wondering how production un-ready these are!? I am looking at >> using Mesos to deploy future stateless services in the next 6 months or so, >> and so I like the idea of adding to that system and the look of the >> configuration that is handled for you to bind nodes together in these >> frameworks. However it feels like for a smallish cluster of production >> ready machines it might be better to deploy them standalone and stay >> observant on the status of such things in the near future, and the >> configuration wins are not that large especially for a small cluster. >> >> >> Any experience and advice on the above would be greatly received! >> >> >> Chris >> >> >> >> >
