You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kapil Arya (JIRA)" <ji...@apache.org> on 2016/04/18 14:30:25 UTC

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

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

Kapil Arya commented on MESOS-4610:
-----------------------------------

Followup cleanup commits:

{code}
commit 9ac2ddae78a26c2730b2a1c15e14f64b17a8583b
Author: Kapil Arya <ka...@mesosphere.io>
Date:   Thu Apr 7 18:24:06 2016 -0400

    Removed unsed headers from master contender/detector files.
    
    Review: https://reviews.apache.org/r/45901

commit a4e11f8186a15a8159ba0eb46335595843e053ba
Author: Kapil Arya <ka...@mesosphere.io>
Date:   Thu Apr 7 18:21:08 2016 -0400

    Removed stale contender/detector files.
    
    Also updated Makefile.am to move contender/detector module library
    declarations into the existing list.
    
    Review: https://reviews.apache.org/r/45900
{code}

> 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
>              Labels: mesosphere
>             Fix For: 0.29.0
>
>
> 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)