[
https://issues.apache.org/jira/browse/QPID-7776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021169#comment-16021169
]
Lorenz Quack commented on QPID-7776:
------------------------------------
Review comments:
* In the documentation:
** The other policies do not have the "Policy" in the <emphasis> part
** I think we should mention that the other flow to disk mechanisms the broker
has (with link) are orthogonal to this.
* For the UI: Any reason we do not use the validValues from the metadata? I
think we do this for example for the LogLevel of the log inclusion rules
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
