[jira] [Commented] (MESOS-4610) MasterContender/MasterDetector should be loadable as modules

["Mark Cavage (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135190#comment-15135190 ] 

Mark Cavage commented on MESOS-4610:
------------------------------------

Review posted here: https://reviews.apache.org/r/43269

> MasterContender/MasterDetector should be loadable as modules
> ------------------------------------------------------------
>
>                 Key: MESOS-4610
>                 URL: https://issues.apache.org/jira/browse/MESOS-4610
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>            Reporter: Mark Cavage
>
> Currently mesos depends on Zookeeper for leader election and notification to slaves, although there is a C++ hierarchy in the code to support alternatives (e.g., unit tests use an in-memory implementation). From an operational perspective, many organizations/users do not want to take a dependency on Zookeeper, and use an alternative solution to implementing leader election. Our organization in particular, very much wants this, and as a reference there have been several requests from the community (see referenced tickets) to replace with etcd/consul/etc.
> This ticket will serve as the work effort to modularize the MasterContender/MasterDetector APIs such that integrators can build a pluggable solution of their choice; this ticket will not fold in any implementations such as etcd et al., but simply move this hierarchy to be fully pluggable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)