[
https://issues.apache.org/jira/browse/MESOS-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060979#comment-14060979
]
Benjamin Hindman commented on MESOS-1584:
-----------------------------------------
Why provide the proxy in the mesos-slave instead of the mesos-master? Are you
suggesting that the scheduler will be running on a slave and therefore it has
easy access to the slave? What about providing a "service" like this on the
master, and then giving each scheduler the list of all the masters instead of
the list of all the ZooKeeper hosts?
> allow slave to proxy scheduler registration in service to master detection
> --------------------------------------------------------------------------
>
> Key: MESOS-1584
> URL: https://issues.apache.org/jira/browse/MESOS-1584
> Project: Mesos
> Issue Type: Improvement
> Components: framework
> Reporter: brian wickman
>
> This is just an idea -- right now each pure language binding will need to
> implement a master detector (which in most cases means your language will
> need zookeeper bindings.)
> Instead of each binding needing to implement a master detector, perhaps the
> slave should support a 'proxy' mode whereby it acts as master detector on
> behalf of a dumber pure language binding. This could also help facilitate
> the launching of replica schedulers. Alternately this could be a separate
> binary but could just as easily live in the slave process.
--
This message was sent by Atlassian JIRA
(v6.2#6252)