qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3286) cluster node went down
Date Mon, 18 Jul 2011 13:35:57 GMT

    [ https://issues.apache.org/jira/browse/QPID-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067026#comment-13067026
] 

Alan Conway commented on QPID-3286:
-----------------------------------

1. Is it possible to monitor the journal file size growth and flush the journal files before
it reach certain limit, so that we can save the brocker going down.

No. If the senders are consistently sending messages faster than the receivers are accepting
them then you will inevitably hit the limit at some point. 

However as in my previous comment, you can avoid broker shutdown: a good solution is to set
a queue limit policy on you're queues with a limit that is lower than the size of your store.
Policy exceptions are synchronized across the broker so if you exceed the limit on a queue,
the sender will receive an exception and the cluster will continue as normal.

2. Is there any limit on journal file size

No.

> cluster node went down
> ----------------------
>
>                 Key: QPID-3286
>                 URL: https://issues.apache.org/jira/browse/QPID-3286
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Clustering
>    Affects Versions: 0.10
>         Environment: Two node persistent cluster using openais. Both nodes are CentOS
5.5.
>            Reporter: sujith paily
>            Assignee: Alan Conway
>            Priority: Critical
>              Labels: adminis, newbie
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> I have configured qpid 0.10 c++ brocker as 2 node persistent cluster. I was worked without
any issue for few hours or sometimes one or two day. But one  node went down after some time
with following error.
> ---------------------------------------
> 2011-05-30 12:55:28 warning Journal "OPC_MESSAGE_QUEUE": Enqueue capacity threshold exceeded
on queue "OPC_MESSAGE_QUEUE".
> 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)
(qpid/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
> --------------------------------------
> But the remaining node is working without any issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message