[jira] [Updated] (QPID-7763) [Java Broker] Flow to disk if allocated direct memory exceeds broker wide broker.flowToDiskThreshold
[ https://issues.apache.org/jira/browse/QPID-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7763: - Fix Version/s: qpid-java-6.1.3 qpid-java-broker-7.0.0 qpid-java-6.0.7 > [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 >Assignee: Alex Rudyy > Fix For: qpid-java-6.0.7, qpid-java-broker-7.0.0, qpid-java-6.1.3 > > > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7763) [Java Broker] Flow to disk if allocated direct memory exceeds broker wide broker.flowToDiskThreshold
[ https://issues.apache.org/jira/browse/QPID-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7763: - Status: Reviewable (was: In Progress) > [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 >Assignee: Alex Rudyy > > 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org