On 26 August 2014 08:49, Jeremy Jongsma <jer...@barchart.com> wrote: > I think it makes sense for each datacenter to stay independently managed > by a local Mesos master. But maybe a framework like Marathon could know > about Marathon frameworks in other datacenters, and a Marathon app config > could specify which datacenters to deploy to. The framework would > coordinate with its peers for deployment. > > Of course, this means any advanced framework scheduler would need to > provide its own distributed coordination/config service (not ideal), so > cross-datacenter discovery/coordination functionality may make sense as a > service provided to frameworks by the Mesos core, even if the master itself > doesn't actively coordinate with other masters. > > This probably requires some non-trivial changes: > > 1) Datacenter-local masters that are aware of other Mesos clusters and > share configuration with them, but only care about configuration that > applies to their own cluster/datacenter. > > 2) A coordination/config service that emphasizes AP over C, at least > across datacenter boundaries. So probably not zookeeper or etcd. >
You can reduce the C via https://issues.apache.org/jira/browse/ZOOKEEPER-1607. -rgs
