qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-7763) [Java Broker] Flow to disk if allocated direct memory exceeds broker wide broker.flowToDiskThreshold
Date Wed, 17 May 2017 14:09:04 GMT

     [ 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message