Re: Cluster-ID mismatch. Stores belong to different clusters

[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