[
https://issues.apache.org/jira/browse/QPID-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021294#comment-16021294
]
ASF subversion and git services commented on QPID-7776:
-------------------------------------------------------
Commit 8fdfbfbd35604399d996f54066bbef77b33f00c8 in qpid-broker-j's branch
refs/heads/master from [~lorenz.quack]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=8fdfbfb ]
QPID-7776: [Java Broker] Address review comments
* update documentation
* use validValues from metadata in UI
> Add flow to disk queue policy
> -----------------------------
>
> Key: QPID-7776
> URL: https://issues.apache.org/jira/browse/QPID-7776
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> It should be possible to configure a queue so that enqueues are always flowed
> to disk, or are flowed to disk when the queue reaches a certain length or
> depth.
> A common use case for this would be a user who has one queue that is used
> _store and forward_ (say for an end of day batch) whilst other queues are
> used 'live'. It will make sense for such a user for to mark the batch's
> queue flow to disk. That way the messages on the batch queue don't
> needlessly clog the Broker's memory leaving it free for intraday work.
> The C++ Broker already has an analogous feature.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
