聚类在ServiceMix的4 [英] Clustering in ServiceMix 4

查看:154
本文介绍了聚类在ServiceMix的4的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想配置Apache ServiceMix的4提供它提到的负载均衡功能的文档(例如此处的 http://servicemix.apache.org/clustering.html )。虽然它的提及,我无法找到确切的路该怎么做。

I'm trying to configure Apache ServiceMix 4 to provide load balancing feature mentioned in it's documentation (for example here: http://servicemix.apache.org/clustering.html). Although it's mentioned, I couldn't find the exact way how to do it.

的想法是有2 ServiceMixes(局域网,例如)与安装在它们相同的OSGi服务。当客户端尝试使用该服务,负载平衡器带他到适当的服务实例的ServiceMixes之一。

The idea is to have 2 ServiceMixes (in LAN, for example) with the same OSGi service installed in them. When client tries to use the service, the load balancer takes him to appropriate service instance on one of the ServiceMixes.

有没有一种简单的方法来做到这一点?

Is there an easy way to do that?

推荐答案

Fabric8( http://fabric8.io/)可以做Karaf / ServiceMix的集群以及更多开箱。它还具有其他群集骆驼组件,如主面料端点

Fabric8 (http://fabric8.io/) can do Karaf/ServiceMix clustering and much more out of the box. It also have additional clustered Camel components such as the master and fabric endpoints

  • http://fabric8.io/gitbook/camelEndpointMaster.html
  • http://fabric8.io/gitbook/camelEndpointFabric.html

有一个集群骆驼例如,证明

There is a clustered Camel example, that demonstrates that

客户端将然后加载提供服务的活动节点之间的平衡。所以,如果你有5个节点,那么它的平衡之中。如果其中一个节点死亡或停止等,那么它只是4仍然活跃的节点之间保持平衡。因此,解决办法是完全弹性和可扩展性。

The client will then load balance between the active nodes that provides the service. So if you have 5 nodes, then it balance among those. If one of the nodes dies or is stopped etc, then it just balance between the 4 still active nodes. So the solution is fully elastic and scalable.

的原理如下图所示:

这篇关于聚类在ServiceMix的4的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆