[rabbitmq-discuss] Feature Req / Bug list
graeme at sudo.ca
Mon Oct 28 20:31:08 GMT 2013
Ran into another interesting issue which I'm not gonna create a full test
case for right now, as I'm trying to focus on clustering problems, but I
thought it was worth mentioning.
It looks like if you have a bunch of persistent queues full of messages
(~10k each in this case), and you delete them via the API and then recreate
them immediately, Rabbit won't have finished deleting messages out of
mnesia / disk, and so they'll reappear with some subset of the messages
that were present before queue deletion.
This is definitely not the behaviour I'd expect, although it makes sense if
queue deletion happens asynchronously. Even so, might be worth revisiting
the behaviour and making sure old messages are purged on queue deletion
before letting a "new" queue with the same name be created.
On Mon, Oct 28, 2013 at 1:22 PM, Michael Klishin <michael at rabbitmq.com>wrote:
> On 29 Oct 2013, at 00:14, Graeme N <graeme at sudo.ca> wrote:
> > I'm going a different direction now anyway, the go amqp libs are easy to
> use and seem performant, so I'm just whipping up a little populator in go.
> Seems to be doing the job, so I think I'm gonna forget about PerfTest for
> Take a look at https://github.com/gocardless/amqpc, too.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss