[MESOS-3574] Support replacing ZooKeeper with replicated log

• Type: Improvement
• Status: Accepted
• Priority: Major
• Resolution: Unresolved
• Component/s: leader election, replicated log
• Labels: mesosphere
• Assignee: Unassigned
• Reporter: Neil Conway
• Created: 02/Oct/15 18:23
• Updated: 26/Nov/18 13:36

Description

It would be useful to support using the replicated log without also requiring ZooKeeper to be running. This would simplify the process of configuring/operating a high-availability configuration of Mesos.

At least three things would need to be done:
1. Abstract away the stuff we use Zk for into an interface that can be implemented (e.g., by etcd, consul, rep-log, or Zk). This might be done already as part of MESOS-1806
2. Enhance the replicated log to be able to do its own leader election + failure detection (to decide when the current master is down).
3. Validate replicated log performance to ensure it is adequate (per Joris, likely needs some significant work)

Issue Links

• incorporates: MESOS-3797 Support replacing Zookeeper with Consul
• is related to: MESOS-1806 Etcd-based master contender/detector module