[
https://issues.apache.org/jira/browse/MESOS-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15616044#comment-15616044
]
Zhitao Li commented on MESOS-3574:
----------------------------------
How will frameworks and agents detect where is, using replicated log? Are
clients expected to hard code a list of master's ip:port and rely on redirect
message from master?
> Support replacing ZooKeeper with replicated log
> -----------------------------------------------
>
> Key: MESOS-3574
> URL: https://issues.apache.org/jira/browse/MESOS-3574
> Project: Mesos
> Issue Type: Improvement
> Components: leader election, replicated log
> Reporter: Neil Conway
> Labels: mesosphere
>
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
