I'm Brenden, an engineer at Airbnb. I'm the one responsible for our Mesos clusters. We run Hadoop, Storm, Chronos, and Marathon. I'm a Mesos contributor, and I'm also the maintainer/contributor for a number of related projects. I've been hacking away on computers since I was old enough to reach the keyboard, and will probably continue to do so as long as I'm allowed.
I'll be giving a talk (and participating in a panel) at MesosCon, sharing some of my experiences. I look forward to meeting many of you fine folks. On Sat, Aug 16, 2014 at 10:20 PM, Sharma Podila <[email protected]> wrote: > > On Sat, Aug 16, 2014 at 6:41 PM, Michael Babineau < > [email protected]> wrote: > >> >> I'm especially interested in multi-datacenter Mesos (either as one >> cluster or coordinating across clusters) -- if anyone has thoughts around >> this, I'd love to chat! >> >> > Depending on the specific needs, different models are possible. Would be > great to chat. > > 1. One Mesos master with slaves added from different datacenters > > Slaves from each data center may be given different attributes to bias > scheduling tasks based on latency, data locality and other characteristics. > Depends on what framework is being used. > > 2. Peer to peer model, a full Mesos cluster in each data center > > A layer written on top or in between them to broker available resources > as a 'lease out' > > 3. Hierarchical model, one datacenter is 'primary' and off-shores tasks to > other datacenters based on load (possibly similar to spilling over to > off-site cloud when on-premise datacenter is full) > 4. A ring of Mesos clusters > > Send task to the datacenter based on consistent hashing of task name/ID, a > la Cassandra clusters' key hashing. Although, one of the previous 3 models > may already achieve the objectives that this model attempts to. > > > Some of these are easier than others. There's going to be other models, I > am sure. > >
