Issues on Zk configuration in Marathon

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 ,

Re: Issues on Zk configuration in Marathon

I think you need to either pin the tasks to some of the slaves (e.g. using marathon "CLUSTER" constraint) so that you can have a static configuration for your zk instances, or you need some type of service discovery. On

Re: Issues on Zk configuration in Marathon

Thanks Lin Shuai Regards, Sam Sent from my iPhone > On Feb 1, 2016, at 10:08 PM, Shuai Lin wrote: > > I think you need to either pin the tasks to some of the slaves (e.g. using > marathon "CLUSTER" constraint) so that you can have a static configuration > for your zk instances, or you need s

Re: Issues on Zk configuration in Marathon

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 ZooKeep