mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yong Tang (JIRA)" <>
Subject [jira] [Commented] (MESOS-4610) MasterContender/MasterDetector should be loadable as modules
Date Thu, 31 Mar 2016 16:46:25 GMT


Yong Tang commented on MESOS-4610:

Can you remove the "/:" at the end of the link? If you click each link you will get 404 with
the extra "/:".

> MasterContender/MasterDetector should be loadable as modules
> ------------------------------------------------------------
>                 Key: MESOS-4610
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>            Reporter: Mark Cavage
>            Assignee: Mark Cavage
>              Labels: mesosphere
> 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
> 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

View raw message