qpid集群配置

深藏阁楼爱情的钟 2022-06-10 05:06 309阅读 0赞

Qpid是基于AMQP的实现。

安装的c++的broker，测试了一下集群的性能。比activeMQ的集群的处理能力强大多了，完全不在一个层次上。

Qpid的集群编译的时候就需要安装好openais这里在一篇文章里已经提到过了。

*High Availability Messaging Clusters provide fault tolerance by ensuring that every broker in a cluster has the same queues, exchanges, messages, and bindings, and allowing a client to fail over to a new broker and continue without any loss of messages if the current broker fails or becomes unavailable. Because all brokers are automatically kept in a consistent state, clients can connect to and use any broker in a cluster. Any number of messaging brokers can be run as one cluster, and brokers can be added to or removed from a cluster while it is in use.*

记得修改/etc/ais/openais.conf的配置，并且开发出其中boardcast的端口5405，iptables里开放出来，要不cluster将出现问题。

最基本的集群启动很简单

命令:

启动第一台

\[root@sample ~\]\# /usr/local/qpid/sbin/qpidd --data-dir /usr/local/qpid/data\_2/ --log-enable info+ --log-to-file /usr/local/qpid/qpidd\_2.log -d --auth 0 -p 5673 --cluster-name 'cluster\_one'

启动第二台

指定一样的cluster-name

--cluster-name 'cluster\_one'

启动如果出现错误

2011-06-26 02:35:40 notice Initializing CPG  
2011-06-26 02:35:40 notice Re-trying CPG initialization.  
2011-06-26 02:35:45 notice Re-trying CPG initialization.  
2011-06-26 02:35:50 notice Re-trying CPG initialization.  
2011-06-26 02:35:55 notice Re-trying CPG initialization.  
2011-06-26 02:36:00 notice Re-trying CPG initialization.  
2011-06-26 02:36:05 critical Unexpected error: Failed to initialize CPG.: try again (6)  
这里多半是由于ais没有启动导致的，qpid是用调用ais来实现cluster的，ais没有启动导致CPG初始化不成功，而出现以上的错误。

通知注意要在ais的group里进行启动

见qpid的文档

On RHEL5, the primary group for the process running qpidd must be the ais group. If you are running qpidd as a service, it is run as the **qpidd** user, which is already in the ais group. If you are running the broker from the command line, you must ensure that the primary group for the user running qpidd is ais. You can set the primary group using **newgrp**:

$ newgrp ais

同时文档里提到了SELINUX

Note

If you are using SELinux, the qpidd process and OpenAIS must have the same SELinux context, or else SELinux must be set to permissive mode. If both qpidd and OpenAIS are run as services, they have the same SELinux context. If both OpenAIS and qpidd are run as user processes, they have the same SELinux context. If one is run as a service, and the other is run as a user process, they have different SELinux contexts.

我都是在shell里启动的，没有出现问题。

启动ais

**service openais start**

如果要禁止SELinux

**setenforce 0**

测试的producer和consumer都是用java实现的。

基本上可以上每秒钟发送到6000个消息，同时两个客户端的接收的稍微差一些。

要知道，服务器是在我的破本子上的VM里安装的。

测试的producer和consumer都是在我的本子上跑的，producer的并发线程1000。

2个consumer，都是在eclipse里跑的，所以在这样的情况下达到这样的程度，个人还是很满意的

有机会试试RabbitMQ的能力，以前问过上海分公司的架构师说是对比过这两个产品，RabbitMQ的性能要强一些，在非集群环境下。

不知道真的假的，RabbitMQ需要先ERlang的虚拟机(可以简单理解类似JVM的东东)。