[jira] [Commented] (MESOS-3797) Support replacing Zookeeper with Consul
[ https://issues.apache.org/jira/browse/MESOS-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971258#comment-14971258 ] Yong Tang commented on MESOS-3797: -- Replacing Mesos with Consul could be part of MESOS-3574, and a short term solution before the implementation of (no-dependency) leader election in Mesos. > Support replacing Zookeeper with Consul > --- > > Key: MESOS-3797 > URL: https://issues.apache.org/jira/browse/MESOS-3797 > Project: Mesos > Issue Type: Improvement > Components: leader election >Reporter: Yong Tang > > Currently Mesos only support Zookeeper for leader election. While Zookeeper > has been widely used it is not actively developed and the configuration of > Zookeeper is often cumbersome or difficult. > There is already an ongoing MESOS-1806 which would replace Zookeeper with > etcd. It would be great if Mesos could support replacing Zookeeper with > Consul for its ease of deployment. > While MESOS-3574 proposed Mesos to do its own leader election and failure > detection, replacing Zookeeper with Consul as a short term solution will > really benefit a lot of existing Mesos users that want to avoid the > dependency of Zookeeper deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3797) Support replacing Zookeeper with Consul
[ https://issues.apache.org/jira/browse/MESOS-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971248#comment-14971248 ] Yong Tang commented on MESOS-3797: -- The implementation of replacing Zookeeper with etcd could help the implementation of replacing Zookeeper with Consul. > Support replacing Zookeeper with Consul > --- > > Key: MESOS-3797 > URL: https://issues.apache.org/jira/browse/MESOS-3797 > Project: Mesos > Issue Type: Improvement > Components: leader election >Reporter: Yong Tang > > Currently Mesos only support Zookeeper for leader election. While Zookeeper > has been widely used it is not actively developed and the configuration of > Zookeeper is often cumbersome or difficult. > There is already an ongoing MESOS-1806 which would replace Zookeeper with > etcd. It would be great if Mesos could support replacing Zookeeper with > Consul for its ease of deployment. > While MESOS-3574 proposed Mesos to do its own leader election and failure > detection, replacing Zookeeper with Consul as a short term solution will > really benefit a lot of existing Mesos users that want to avoid the > dependency of Zookeeper deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
