Interesting How do you handle / prevent 'brain-split' situations for the masters / zookeeper? (two half-clusters not 'seeing' each other - effectively behaving as two separate clusters)
(Y) On Aug 26, 2014, at 5:43 PM, Justin Holmes <[email protected]> wrote: > Hi > > We have been running Mesos in Google Compute with slaves in us-central1 and > europe-west1 with masters in europe-west1, response times between the zones > have been around 100/110ms. > > I am interested in running masters across zones and will evaluate > DRBD/Ceph/GlusterFS for multi-site master. > > I am also wondering if anyone has tuned master election with Zookeeper across > zones and also can we switch out the Zookeeper dependency and use > etcd/Cassandra > > Kind regards > > > On 26 August 2014 15:19, Yaron Rosenbaum <[email protected]> wrote: > Hi > > Here's a crazy idea: > Is it possible / has anyone tried to run Mesos where the slaves are in > radically different network zones? For example: A few slaves on Azure, a few > slaves on AWS, and a bunch of other slaves on premises etc. > Assuming it's possible, is it possible to define resource requirements for > tasks, in terms of 'access to network resource A with less than X latency and > throughput between i and m' for example? > Masters would probably have to be 'close' to each other, to prevent > 'brain-splits', true or not ? > If so, then how does one assure Master HA ? > > I've been thinking about this for a while, and can't find a reason 'why not'. > > Please share your thoughts on the subject. > > (Y) > > > > > -- > Justin Holmes > Consultant > > Open Credo Ltd – Delivering emerging technology today > > Mobile: +44 (0) 7863173405 > Main: +44 (0) 20 3603 2680 > > [email protected] > http://twitter.com/DevOpsScientist > http://www.opencredo.com > > > Registered Office: 5-11 Lavington St., London SE1 0NZ. > Registered in UK. No 3943999 > > > > If you have received this e-mail in error please accept our apologies, > destroy it immediately and it would be greatly appreciated if you notified > the sender. It is your responsibility to protect your system from viruses > and any other harmful code or device. We try to eliminate them from e-mails > and attachments; but we accept no liability for any that remain. We may > monitor or access any or all e-mails sent to us.
