mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] [Comment Edited] (MESOS-4610) MasterContender/MasterDetector should be loadable as modules
Date Mon, 28 Mar 2016 15:23:25 GMT


ANURAG SINGH edited comment on MESOS-4610 at 3/28/16 3:22 PM:

We've proceeded further with the review and here's the updated list of changes: Added MasterContender and MasterDetector abstract classes. Changed MasterDetector/Contender namespace. Removed unnecessary MasterContender and MasterDetector
definitions. Moved contender and detector definitions into separate
directories. Instead of keeping standalone and zookeper contender/detector
definitions and implementations in the same file, separated them. Also
made the necessary changes in users of class headers to point to the
new locations. Moved functions in promises to a common header file. Added functions in promises to the collect header. Added support for contender and detector modules. Added createFromModule methods to MasterContender and
MasterDetector. Added master_detector and master_contender flags.

was (Author: anurag.prakash.singh):
We've proceeded further with the review and here's the updated list of changes:

> 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