[
https://issues.apache.org/jira/browse/MESOS-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176526#comment-15176526
]
ANURAG SINGH commented on MESOS-4610:
-------------------------------------
Hi,
I work with Mark and will be continuing this effort. I've uploaded
https://reviews.apache.org/r/44287/, https://reviews.apache.org/r/44288/ and
https://reviews.apache.org/r/44289/ - it's essentially Mark's patch broken up
into parts per Joseph's suggestions. The one addition I've made is to add
master_contender and master_detector flags to allow users to specify the
contender/detector modules to use.
> 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
> Assignee: 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)
