Hey Mikhail,
IIRC the configuration options are a bit limited in that you can't
configure a queue such that the queue itself survives restarts but
*force* messages not to be - in other words I think that it will always
honour the message durability setting, which is I think durable by
default. So basically you can't do what you want in a *transparent* way.
However if you have control of the message producer and are able to
request that producers set message durability to false then I think you
can achieve what you want.
For proton doing
pn_message_set_durable(message, 0);
Should (I think) do the trick (I haven't tried it though).
TBH I think it would be nice to have a bit more control over durability
options so that queue and message durability could be configured
separately they are *not* the same thing, if you own the message
producers you can work around this as above, but if not, or if you have
lots of producer systems it's a pain 'cause if one of them doesn't set
message durability to false you can potentially fill stores up
unexpectedly - or worse.
HTH,
Frase
On 04/09/15 06:58, Michael Ivanov wrote:
Sorry to intrude into your discussion, but I have related question.
You have mentioned that the messages can be both durable and non-durable.
How this is controlled in proton? I need all my durable queues to be
persistend over qpidd restart but I don't care about messages.
When I have installed linearstore all my queues were persistent, but
it seems for these queues all messages went through the disk storage
which slowed down the operation quite noticeably.
Best regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
