我怎么集群S​​erviceMix的？

问题描述

我要寻找关于如何集群中的ServiceMix解决一些初步的指针。基本上，我需要的是：

I am looking for some initial pointers on how to cluster a ServiceMix solution. Basically what I need is:

• 具有2个（或以上）ServiceMix的情况下我的服务需求的路由和共享负载


• 如果一个实例失败，其他（S）继续担任


• 如果失败的一个起死回生，它加入了党

在搜索信息，混淆了我，因为

Searching for information confuses me since

• 一些参考（如http://trenaman.blogspot.fi/2010/04/four-things-you-need-to-know-about-new.html)谈JBI集群引擎，我不希望使用JBI。支持是pcated德$ P $，是否有单独的非JBI集群引擎或者是怎么回事...？


• 我看到很多关于提到DOSGi。我需要的所有担心我的简单的头，如果我想实现集群ServiceMix的？

• some references (eg. http://trenaman.blogspot.fi/2010/04/four-things-you-need-to-know-about-new.html) talk about "JBI cluster engine". I don't want to use JBI. Support for it is deprecated. Is there a separate "Non-JBI cluster engine" or what is going on...?
• I see a lot of mentions about "DOSGi". Do I need to worry my simple head with all that if I want to achieve clustered ServiceMix?

我的解决方案将可能有相互使用JMS队列通信的几捆。我应该在这种情况下的只是有2个独立的ServiceMix实例（谁不知道对方的）。难道这不是最简单的选择？我看到故障转移配置一些支持（http://servicemix.apache.org/docs/4.5.x/users-guide/failover.html)但是这会真的给什么好处（我缺少的东西）？还有这种故障转移配置不与负载平衡，因为只有一个实例充当请求帮助。

My solution will probably have a few bundles that communicate with each other using JMS queues. Should I in that case just have 2 independent ServiceMix instances (who do not know of each other). Wouldn't that be the simplest option? I see some support for a failover configuration (http://servicemix.apache.org/docs/4.5.x/users-guide/failover.html) but what benefits would that really give (am I missing something)? Also this failover configuration does not help with load balancing since just one instance is serving requests.

推荐答案

这听起来一样，你需要的是并行运行，没有专门配置的故障切换2 ServiceMix的实例。故障转移是有，如果你想实例的集群，其中只有一个服务的要求。

From what it sounds like, all you need is two ServiceMix instances running side by side with no failover specifically configured. Failover is there if you want a cluster of instances, only one of which services requests.

忽略JBI的东西 - 这是传统。分布式OSGi是在你所描述的情况下，用一个红色的鲱鱼。

Ignore the JBI stuff - it's legacy. Distributed OSGi is a red herring in the use case that you have described.

由于boday表明，酒窖用于均匀地Karaf / ServiceMix的实例的逻辑组管理包的安装，让您可以从一个位置进行管理，而不是用手上的每个实例安装新版本。

As boday suggests, Cellar is used to manage the installation of your bundles uniformly across a logical group of Karaf/ServiceMix instances, so you can manage them from one location as opposed to installing new versions on each instance by hand.

这篇关于我怎么集群S​​erviceMix的？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！