[
https://issues.apache.org/jira/browse/QPID-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996417#comment-15996417
]
ASF subversion and git services commented on QPID-7763:
-------------------------------------------------------
Commit 2b91b4419841fb84bb97028d6995f7f125570412 in qpid-broker-j's branch
refs/heads/6.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=2b91b44 ]
QPID-7763: [Java Broker] Flow to disk if allocated direct memory exceeds broker
wide broker.flowToDiskThreshold
(cherry picked from commit 07ea26e7b8fdc24621fcde04949df633186fa5a0)
> [Java Broker] Flow to disk if allocated direct memory exceeds broker wide
> broker.flowToDiskThreshold
> ----------------------------------------------------------------------------------------------------
>
> Key: QPID-7763
> URL: https://issues.apache.org/jira/browse/QPID-7763
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
>
> Currently the broker.flowToDiskThreshold is compared against the size used by
> messages on queues.
> However, the intent was to have a mechanism for preventing the broker going
> out of direct memory. For this it is much more interesting to observe how
> much direct memory the QpidByteBuffers use. The two numbers can easily differ
> since the QBB can be sparsely populated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
