And for discovery of other nodes in the Paxos group. The work on modularizing/decoupling Zookeeper is a prerequisite for having the replicated log perform leader election itself. <- That would merely be another implementation of the interface we will introduce in the process:
https://issues.apache.org/jira/browse/MESOS-3574 On Tue, Sep 6, 2016 at 11:31 AM, Avinash Sridharan <avin...@mesosphere.io> wrote: > Also, I think, the replicated log itself uses Zookeeper for leader > election. > > On Tue, Sep 6, 2016 at 12:15 PM, Zameer Manji <zma...@apache.org> wrote: > >> If we use the replicated log for leader election, how will frameworks >> detect the leading master? Right now the scheduler driver uses the >> MasterInfo in ZK to discover the leader and detect leadership changes. >> >> On Mon, Sep 5, 2016 at 10:18 AM, Dario Rexin <dre...@apple.com> wrote: >> >>> If we go and change this, why not simply remove any dependencies to >>> external systems and simply use the replicated log for leader election? >>> >>> On Sep 5, 2016, at 9:02 AM, Alex Rukletsov <a...@mesosphere.com> wrote: >>> >>> Kant— >>> >>> thanks a lot for the feedback! Are you interested in helping out with >>> Consul module once Jay and Joseph are done with modularizing patches? >>> >>> On Mon, Sep 5, 2016 at 8:50 AM, Jay JN Guo <guojian...@cn.ibm.com> >>> wrote: >>> >>>> Patches are currently under review by @Joseph and can be found at the >>>> links provided by @haosdent. >>>> >>>> I took a quick look at Consul key/value HTTP APIs and they look very >>>> similar to Etcd APIs. You could actually reuse our Etcd module >>>> implementation once we manage to push the module into Mesos community. >>>> >>>> The only technical problem I could see for now is that Consul does not >>>> support `POST` with incremental key index. We may need to leverage >>>> `?cas=<index>` operation in Consul to emulate the behaviour of joining a >>>> key group. >>>> >>>> We could have a discussion on how to implement Consul HA module. >>>> >>>> cheers, >>>> /J >>>> >>>> >>>> ----- Original message ----- >>>> From: haosdent <haosd...@gmail.com> >>>> To: user <user@mesos.apache.org> >>>> Cc: Jay JN Guo/China/IBM@IBMCN >>>> Subject: Re: what is the status on this? >>>> Date: Sun, Sep 4, 2016 6:10 PM >>>> >>>> Jay has some patches for de-couple Mesos with Zookeeper >>>> >>>> https://issues.apache.org/jira/browse/MESOS-5828 >>>> https://issues.apache.org/jira/browse/MESOS-5829 >>>> >>>> I think it should be possible to support consul by custom modules after >>>> jay's work done. >>>> >>>> On Sun, Sep 4, 2016 at 6:02 PM, kant kodali <kanth...@gmail.com> >>>> wrote: >>>> >>>> Hi Alex, >>>> >>>> We have some experienced devops people here and they all had one thing >>>> in common which is Zookeeper is a pain to maintain. In fact we refused to >>>> bring in new tech stacks that require Zookeeper such as Kafka for example. >>>> so we desperately in search for alternative preferably using consul. I just >>>> hear lot of positive response when comes it consul. It will be great to see >>>> mesos and consul working together in which we would be ready to jump at it >>>> and make a switch for YARN to Mesos. >>>> >>>> Thanks, >>>> Kant >>>> >>>> >>>> >>>> >>>> On Wed, Aug 31, 2016 1:03 AM, Alex Rukletsov a...@mesosphere.com >>>> wrote: >>>> >>>> Kant— >>>> >>>> mind telling us what is your use case and why this ticket is important >>>> for you? It will help us prioritize work. >>>> >>>> On Fri, Aug 26, 2016 at 2:46 AM, tommy xiao <xia...@gmail.com> wrote: >>>> >>>> Hi guys, i always focus on t his case. but good news is etcd always >>>> have patchs. so the coming consul is very easy, just need some time to do >>>> coding on it. if you have interesting it? let us collaborate it. >>>> >>>> 2016-08-26 8:11 GMT+08:00 Joseph Wu <jos...@mesosphere.io>: >>>> >>>> There is no timeline as no one has done any work on the issue. >>>> >>>> >>>> On Thu, Aug 25, 2016 at 4:54 PM, kant kodali <kanth...@gmail.com> >>>> wrote: >>>> >>>> Hi Guys, >>>> >>>> I see this ticket and other related tickets should be part of sprints >>>> in 2015 and it is still not resolved yet. can we have a timeline on this? >>>> This would be really helpful >>>> >>>> https://issues.apache.org/jira/browse/MESOS-3797 >>>> >>>> Thanks! >>>> >>>> >>>> >>>> -- >>>> Deshi Xiao >>>> Twitter: xds2000 >>>> E-mail: xiaods(AT)gmail.com >>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> Haosdent Huang >>>> >>>> >>>> >>>> >>> >> > > > -- > Avinash Sridharan, Mesosphere > +1 (323) 702 5245 >
