qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fraser Adams <fraser.ad...@blueyonder.co.uk>
Subject Re: Message auditing in C++ broker
Date Wed, 12 Mar 2014 19:32:41 GMT
I've got nothing much constructive to add to this thread I'm afraid 
except to plead:
can any features in this general vein be made extremely switch-off-able?

My primary requirement is for things to be as fast as possible, so 
features that might interfere with that make me twitchy.

Basically I can tolerate moderate message loss and I run in memory 
non-durable circular queues more or less universally.

In precis I'm fairly agnostic about this feature provided it has zero 
impact in message throughput performance.

On 12/03/14 18:16, Jakub Scholz wrote:
> On Wed, Mar 12, 2014 at 6:30 PM, Gordon Sim <gsim@redhat.com> wrote:
>> The journal obviously already records the enqueues and dequeues, it just
>> doesn't keep them around. One option might be to have a modified
>> journal/store that kept the data for longer in some way or moved it into
>> some other repository before removing it from the journals themselves.
> Having something like the linear store move the "used" journal files to
> some kind of archive instead of deleting them / reusing them sounds
> similar. The questions is whether the store is flexible enough to contain
> the details like timestamps or some kind of links to connections which
> enqueued / dequeued the messages.

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message