[MESOS-4610] MasterContender/MasterDetector should be loadable as modules

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: master
• Labels: mesosphere
• Sprint: Mesosphere Sprint 29
• Assignee: Mark Cavage
• Reporter: Mark Cavage
• Shepherd: Kapil Arya
• Created: 05/Feb/16 18:55
• Updated: 26/Nov/18 12:21
• Resolved: 26/Nov/18 12:21

Description

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.

Issue Links

• blocks: MESOS-5106 Improve test_http_framework so it can load master detector from modules
• relates to: MESOS-5828 Modularize Network in replicated_log
• relates to: MESOS-5829 Mesos should be able to consume module for replicated_log
• relates to: MESOS-1806 Etcd-based master contender/detector module