Mesos的“主"和“从"节点可以部署在同一台机器上吗? [英] Can Mesos 'master' and 'slave' nodes be deployed on the same machines?

问题描述

是否可以将Apache Mesos主"节点与Mesos从属"节点并置在同一台计算机上?同样(对于高可用性(HA)部署)，可以将Mesos主"选举中使用的Apache Zookeeper节点与Mesos从"节点部署在同一台计算机上吗?

Can Apache Mesos 'master' nodes be co-located on the same machine as Mesos 'slave' nodes? Similarly (for high-availability (HA) deploys), can the Apache Zookeeper nodes used in Mesos 'master' election be deployed on the same machines as Mesos 'slave' nodes?

Mesos建议将3个主服务器"用于HA部署，而Zookeeper建议将5个节点用于其法定选举系统.最好让这些服务沿着Mesos的从属"进程运行，而不是将8台计算机提交给有效的非生产性"任务.

Mesos recommends 3 'masters' be used for HA deploys, and Zookeeper recommends 5 nodes be used for its quorum election system. It would be nice to have these services running along side Mesos 'slave' processes instead of committing 8 machines to effectively 'non-productive' tasks.

如果这样的设置可行，那么这种设置的利弊是什么?

If such a setup is feasible, what are the pros/cons of such a setup?

谢谢！

推荐答案

您绝对可以在同一节点上运行主，从和zk进程.您甚至可以在同一节点上运行多个主进程和从属进程，只要为它们提供每个唯一的端口即可，但这仅对测试集群有用.

You can definitely run a master, slave, and zk process all on the same node. You can even run multiple master and slave processes on the same node, provided you give them each unique ports, but that's only useful for a test cluster.

通常，我们建议在与主服务器相同的节点上运行ZK，但是，如果您有额外的ZK，则可以在从服务器上运行它们，或者只要您认为合适，就可以混合搭配，只要所有主/从/框架节点可以到达ZK节点，所有从节点都可以到达主节点.

Typically we recommend running ZK on the same nodes as your masters, but if you have extra ZKs, you can certainly run them on slaves, or mix-and-match as you see fit, as long as all master/slave/framework nodes can reach the ZK nodes, and all slaves can reach the masters.

对于较小的群集(小于10个节点)，在每个主服务器上运行从属进程可能是有意义的，尤其是因为备用主服务器不会做很多事情.即使是小型集群的活动主服务器，也仅使用少量的CPU，内存和网络资源.只需确保调整该从属服务器上的--resources即可解决主服务器的资源使用情况.

For a smaller cluster (<10 nodes) it could make sense to run a slave process on each master, especially since the standby masters won't be doing much. Even an active master for a small cluster uses only a small amount of cpu, memory, and network resources. Just make sure you adjust the --resources on that slave to account for the master's resource usage.

一旦群集变得更大(尤其是> 100个节点)，去往/来自主服务器的网络流量及其cpu/内存利用率将变得非常重要，以至于您不想在与主服务器相同的节点上运行mesos从服务器.掌握.即使大规模，也可以将ZK与您的主人共址.

Once your cluster grows larger (especially >100 nodes) the network traffic to/from the master as well as its cpu/memory utilization becomes significant enough that you wouldn't want to run a mesos slave on the same node as the master. It should be fine to co-locate ZK with your master even at large scale.

您没有特别询问，但我还将讨论在何处运行框架计划程序(例如Spark，Marathon或Chronos).这些组件可以与任何其他组件放置在同一位置，但是它们实际上仅需要能够到达主节点和zk节点，因为与从属节点的所有通信都通过主节点进行.一些客户在主节点上运行调度程序，一些客户在边缘节点上运行调度程序(这样用户就无法访问从节点)，而其他客户则使用Marathon之类的元框架在从节点上运行其他调度程序作为Mesos任务.

You didn't specifically ask, but I'll also discuss where to run your framework schedulers (e.g. Spark, Marathon, or Chronos). These could be co-located with any of the other components, but they only really need to be able to reach the master and zk nodes, since all communication to slaves goes through the master. Some customers run the schedulers on master nodes, some run them on edge nodes (so users don't have access to the slaves), and others use meta-frameworks like Marathon to run other schedulers on slaves as Mesos tasks.

这篇关于Mesos的“主"和“从"节点可以部署在同一台机器上吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！