此内容没有您所选择的语言版本。

2.2.3. MCollective


MCollective is used for any node host communications or interactions with either the broker host or other nodes. This can include gear placement or removal.
Use the following command to verify that a broker can communicate with all node hosts:
# oo-mco ping
broker.mydomain.com                        time=134.85 ms
node.mydomain.com                          time=541.41 ms
node1.mydomain.com                         time=572.76 ms


---- ping statistics ----
3 replies max: 572.76 min: 134.85 avg: 416.34
Copy to Clipboard Toggle word wrap
All configured node hosts should be represented in the output. If you do not see a node host as expected, verify that the network and clock settings are configured correctly for that node host.

Note

If the oo-mco ping command is not running successfully, it could be that openshift-origin-util-scl is not properly installed on your machine, or that oo-mco ping is missing. Install the openshift-origin-util-scl package in order to run the command.
Communication between broker and node hosts is logged in the following files:
  • /var/log/openshift/node/ruby193-mcollective.log on node hosts
  • /var/log/openshift/broker/ruby193-mcollective-client.log on broker hosts
Communication that is dropped due to exceeding TTL is also logged in these files.
MCollective actions performed on the node can also log more details in /var/log/openshift/node/platform.log and /var/log/openshift/node/platform-trace.log.
If necessary, you can determine on which node host an application is created using the dig or host command, with the application's hostname.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat