This is what I sent to Cory, but not to the mailing list: In my mind, most of the issues were with Storm itself, rather than Mesos. One annoying thing is that Nimbus is stateful (no HA), so you have to figure out a way to manage the assets on disk in a safe manner.
We also used reserved resources for Storm (via Mesos roles), because we were multi-tenant. Without this, it might make for a bad experience (i.e., topologies wouldn't be able to launch correctly due to insufficient resource offers). On Tue, Jan 20, 2015 at 9:51 PM, Srinivas Murthy <srinimur...@gmail.com> wrote: > Brenden, could you please elaborate a bit on those shortcomings :-) > > On Tue, Jan 20, 2015 at 11:06 AM, Brenden Matthews <bren...@diddyinc.com> > wrote: > >> Hi Cory, >> >> We were using the project in production at Airbnb. It may have some >> shortcomings, but it does, in fact, work. >> >> >>> Hello all! >>> I'm interested in Storm on Mesos, but my coworkers don't wanna be guinea >>> pigs. Is anyone using mesos/storm <https://github.com/mesos/storm> in >>> production? I see the repo is at least active. :) >>> >>> >>> -- >>> Cory Watson >>> Principal Infrastructure Engineer // Keen IO >> >> >
