On 09/24/2010 09:16 AM, Jason Stelzer wrote:
Hi, I'm reaching out for a little help and pointers with regard to
qpid clustering.
I'm coming into this with nearly zero qpid experience so I will try to
be as complete as possible. I am attempting to set up a qpid cluster
so that we can scale out our qpid clients across multiple qpid
servers. Is it best practice to have a primary enqueue node and
dequeue from the secondary nodes in the cluster?
The cluster is active-active, you can enqueue and dequeue on any nodes in the
cluster.
My understanding is that replication is geared more for fault
tolerance and disaster recovery, and that clustering is geared towards
supporting large numbers of concurrent activity.
The cluster is geared towards fault tolerance rater than load sharing. All the
brokers effectively do all the work for every client of the cluster regardless
of where the client is connected, so adding more nodes won't enable the cluster
to handle a greater volume of messages - it will increase the clusters tolerance
for failures however.
I am currently working on getting qpid clustering working as described here:
https://cwiki.apache.org/qpid/starting-a-cluster.html
I am running qpid v 0.5 on Fedora 12. I have the following rpms installed:
qpidc-0.5.829175-2.fc12.x86_64
qpidd-0.5.829175-2.fc12.x86_64
qpidd-cluster-0.5.829175-2.fc12.x86_64
When I start qpidd and pass the --cluster-name=TEST_CLUSTER option,
qpidd aborts with the following error:
Starting Qpid AMQP daemon: Daemon startup failed: Cannot join CPG
group DEV_CLUSTER: try again (6)
I believe I have corosync and pacemaker working.
If I start corosync, it takes a bit of time before the crm commands
work, but once everything spins up I don't see any warnings when I
run:
crm_verify -L
(no output/warnings)
crm configure show
node edisondev3
property $id="cib-bootstrap-options" \
dc-version="1.0.5-ee19d8e83c2a5d45988f1cee36d334a631d84fc7" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
stonith-enabled="false" \
stonith-enable="false"
I've double checked my bindnetaddress in corosync.conf. It lines up
with the wiki article and agrees with the output of /sbin/route.
I double checked my uidgid.d/qpid file. Initially I had the uid wrong
and was getting a security error when I started qpid. Now that I have
the correct uid/gid, I am seeing the 'try again' error above.
Any tips would be appreciated.
Did you check your firewall and selinux settings? If it still doesnt work send
the follow:
# getenforce
# iptables -L
# ifconfig
# cat /etc/corosync
# tail -n +0 /etc/corosync/corosync.conf /etc/corosync/uidgid.d/*
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
