Thanks for the answers, Gordon. Comments inline, if Outlook cooperates. > -----Original Message----- > From: Gordon Sim [mailto:[email protected]] > Sent: Friday, July 24, 2009 11:19 AM > To: [email protected] > Cc: Jason Copeland > Subject: Re: Journal Full Error > > Sandy Pratt wrote: > > I'm experimenting with the qpidd broker supplied with Fedora 10 > (qpidd (qpidc) version 0.5 - the install should be up to date as of > yesterday). > > Basically, I'm having a problem where I've been able to enqueue > enough messages that my journal is full and I can't start the broker > because of this. This is contrary to my understanding of how > persistent queues were supposed to work, in a number of ways: > > > > 1) I thought producers were not allowed to commit messages past the > 80% full point. > > That was be understanding also. Kim any thoughts on how the journal > could allow itself to get into a state where it can't be recovered? > > > 2) I thought the flow-to-disk policy would result in excess messages > being accepted into a slower interim storage, not being rejected or > causing the broker to crash. > > Transient messages are stored in a different storage if they exceed the > defined queue policy limit, and that grows as needed. Persistent > messages however are written to the journal regardless of whether the > queue policy limit which currently has a fixed size that must be > defined > up front. > > > > > 3) It appears as though I was able to crash the broker and cause the > apparent loss of acked messages simply by sending the broker too many? > > Could you give a bit more detail on this point?
[Sandy Pratt] I was hoping that regardless of whether I could write to the queue, I would still be able to start the broker and read them, or get them out somehow -- because having committed the messages to the broker, that might well be their sole home. If I can't get them out, then I've lost them. Is there a procedure for extracting messages from a full journal? [Sandy Pratt] snip... > > I can sort of understand this, although it means flow-to-disk is not > functioning for my queue, I suppose. > > As above, the persistent messages would always be written to the > journal > and it has a fixed size. > > The 'flow-to-disk' policy is probably confusingly named and > inadequately > described. It really just releases the message content from memory when > a queue hits a particular limit; where those messages are durable > anyway > nothing else is done. If however the messages are transient they are > stored elsewhere and can then be reloaded for delivery. [Sandy Pratt] Understood, thank you. Flow-to-disk is a property of non-persistent messages/queues, not persistent ones. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
