[
https://issues.apache.org/jira/browse/MESOS-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208227#comment-14208227
]
Alexander Rukletsov commented on MESOS-1546:
--------------------------------------------
I think we would also like to update the whitelist on the fly (similar to how
slave whitelisting works right now). A possible solution is to have
{{--masters}} point to a JSON file which is reloaded after each update.
> Introduce an optional master whitelist for replicated log based registrar.
> --------------------------------------------------------------------------
>
> Key: MESOS-1546
> URL: https://issues.apache.org/jira/browse/MESOS-1546
> Project: Mesos
> Issue Type: Improvement
> Components: master, replicated log
> Reporter: Jie Yu
> Labels: MesosConHack, twitter
>
> When using replicated log as the storage back-end for registrar, we currently
> rely on ZooKeeper to discover replicas (see ZooKeeperNetwork in
> src/log/network.hpp). We simply broadcast Paxos messages to all replicas in
> the ZooKeeperNetwork.
> There is a security concern using this approach. For example, say initially
> there are 3 masters and the quorum size is 2. Now, if a 4th master is
> accidentally added and joined the ZooKeeperNetwork, we will then operate at 4
> replicas with quorum size 2. This could lead to inconsistency in the
> replicated log (and thus registrar).
> The idea here is to introduce a whitelist for masters. We still use
> ZooKeeperNetwork to discover replicas. However, when broadcasting Paxos
> messages in the replicated log, we check the whitelist and make sure we don't
> send Paxos messages to a master that is not in this whitelist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
