You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by sujith <su...@perfomix.com> on 2011/05/30 06:46:09 UTC
Cluster-ID mismatch. Stores belong to different clusters
Hi
Please help me. Got following error while starting a qpid cluster with
persistent store
Daemon startup failed: Cluster-ID mismatch. Stores belong to different
clusters.
--
View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/Cluster-ID-mismatch-Stores-belong-to-different-clusters-tp6417839p6417839.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Cluster-ID mismatch. Stores belong to different clusters
Posted by Alan Conway <ac...@redhat.com>.
On 05/30/2011 10:04 AM, sujith wrote:
> Thank you. My issue is fixed. But I have a new issue.
> When the queue size exceeds the persistent storage size I am getting
> following exception
> --------------------------------------------------------------------------------------------------------------------------
> warning Journal "OPC_MESSAGE_QUEUE": Enqueue capacity threshold exceeded on
> queue "OPC_MESSAGE_QUEUE".
> -------------------------------------------------------------------------------------------------------------------
>
> After sometime one node getting down with following errors
>
> ------------------------------------------------------------------------------------------------------------------------------------
> 2011-05-30 12:55:28 error Unexpected exception: Enqueue capacity threshold
> exceeded on queue "OPC_MESSAGE_QUEUE". (JournalImpl.cpp:587)
> 2011-05-30 12:55:28 error Connection 192.168.1.138:5672-192.168.1.10:58839
> closed by error: Enqueue capacity threshold exceeded on queue
> "OPC_MESSAGE_QUEUE". (JournalImpl.cpp:587)(501)
> 2011-05-30 12:55:28 critical cluster(192.168.1.138:6321 READY/error) local
> error 11545 did not occur on member 192.168.1.139:25161: Enqueue capacity
> threshold exceeded on queue "OPC_MESSAGE_QUEUE".
> (JournalImpl.cpp:587)
> 2011-05-30 12:55:28 critical Error delivering frames: local error did not
> occur on all cluster members : Enqueue capacity threshold exceeded on queue
> "OPC_MESSAGE_QUEUE". (JournalImpl.cpp:587) (qpi
> d/cluster/ErrorCheck.cpp:89)
> 2011-05-30 12:55:28 notice cluster(192.168.1.138:6321 LEFT/error) leaving
> cluster QCLUSTER
> 2011-05-30 12:55:28 notice Shut down
> -----------------------------------------------------------------------------------------------------------------
>
> My queue limit policy is ring-strict
>
> But when I run this on non clustered set up, I don't have any issue even
> queue size exceeds persistent storage size.
>
I think your policy limit is too big for your store size. The policy limit.
There is some overhead in storing messages so the store size needs to be bigger
than the total message data size. I don't know the formula to calculate this,
perhaps someone else on the list can chime in.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Cluster-ID mismatch. Stores belong to different clusters
Posted by sujith <su...@perfomix.com>.
Thank you. My issue is fixed. But I have a new issue.
When the queue size exceeds the persistent storage size I am getting
following exception
--------------------------------------------------------------------------------------------------------------------------
warning Journal "OPC_MESSAGE_QUEUE": Enqueue capacity threshold exceeded on
queue "OPC_MESSAGE_QUEUE".
-------------------------------------------------------------------------------------------------------------------
After sometime one node getting down with following errors
------------------------------------------------------------------------------------------------------------------------------------
2011-05-30 12:55:28 error Unexpected exception: Enqueue capacity threshold
exceeded on queue "OPC_MESSAGE_QUEUE". (JournalImpl.cpp:587)
2011-05-30 12:55:28 error Connection 192.168.1.138:5672-192.168.1.10:58839
closed by error: Enqueue capacity threshold exceeded on queue
"OPC_MESSAGE_QUEUE". (JournalImpl.cpp:587)(501)
2011-05-30 12:55:28 critical cluster(192.168.1.138:6321 READY/error) local
error 11545 did not occur on member 192.168.1.139:25161: Enqueue capacity
threshold exceeded on queue "OPC_MESSAGE_QUEUE".
(JournalImpl.cpp:587)
2011-05-30 12:55:28 critical Error delivering frames: local error did not
occur on all cluster members : Enqueue capacity threshold exceeded on queue
"OPC_MESSAGE_QUEUE". (JournalImpl.cpp:587) (qpi
d/cluster/ErrorCheck.cpp:89)
2011-05-30 12:55:28 notice cluster(192.168.1.138:6321 LEFT/error) leaving
cluster QCLUSTER
2011-05-30 12:55:28 notice Shut down
-----------------------------------------------------------------------------------------------------------------
My queue limit policy is ring-strict
But when I run this on non clustered set up, I don't have any issue even
queue size exceeds persistent storage size.
--
View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/Cluster-ID-mismatch-Stores-belong-to-different-clusters-tp6417839p6419262.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org
Re: Cluster-ID mismatch. Stores belong to different clusters
Posted by Alan Conway <ac...@redhat.com>.
On 05/30/2011 12:46 AM, sujith wrote:
> Hi
>
> Please help me. Got following error while starting a qpid cluster with
> persistent store
>
> Daemon startup failed: Cluster-ID mismatch. Stores belong to different
> clusters.
>
To ensure data is not corrupted, qpid marks each brokers store with a UUID when
the cluster starts. If you mix stores from different clusters you'll get the
error above.
Stores are marked "dirty" while the cluster is running, so old data won't be
used after restart.
To shut the cluster down cleanly use "qpid-cluster -k". That way all brokers
will mark the stores "clean" for restart.
To start up correctly when some brokers crash, set in config:
cluster-size=N (number of members in your cluster)
On start-up the brokers will wait till all N members are present before deciding
what store to use, so they will correctly chose a clean store.
If you want to erase an old store, you need to erase the stores and cluster
identity for _all_ brokers before starting:
rm -rf /var/lib/qpidd/*
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org