It's interesting idea, but if you use ZooKeeper for Marathon or Mesos discovery you might easily end up in chicken-egg problem. You would like to start Marathon, but there's no ZooKeeper available until you start Marathon.
If 3 ZooKeepers aren't enough for you, you might consider deploying ZooKeeper in observer mode via Marathon. http://zookeeper.apache.org/doc/trunk/zookeeperObservers.html On 2 February 2016 at 12:24, Sam <[email protected]> wrote: > Thanks Lin Shuai > > Regards, > Sam > > Sent from my iPhone > > On Feb 1, 2016, at 10:08 PM, Shuai Lin <[email protected]> wrote: > > I think you need to either pin the tasks to some of the slaves (e.g. using > marathon "CLUSTER" > <https://mesosphere.github.io/marathon/docs/constraints.html#cluster-operator> > constraint) so that you can have a static configuration for your zk > instances, or you need some type of service discovery. > > On Mon, Feb 1, 2016 at 9:09 PM, Sam <[email protected]> wrote: > >> Hello guys >> One quick question in Marathon with Mesos, >> We are trying to deploy Zk with Marathon to make sure that Zk is always >> available no matter one of nodes crashed. For example : we got Zk1,Zk2 and >> Zk3, Zk1 need to have IP address of Zk2 and Zk3; Zk2 need to have IP >> address of Zk1 and Zk3 , same to Zk3 . The issue is when one of them >> crashed , and Marathon spin up new Zk, how to have old IP address >> configuration set into new instance ? I think this is issue to all App >> cluster that need to have each other configuration respectively. >> Looking forward to having solution to get it done . Appreciate >> >> Regards, >> Sam >> >> Sent from my iPhone > > >
