qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7763) [Java Broker] Flow to disk if allocated direct memory exceeds broker wide broker.flowToDiskThreshold
Date Fri, 05 May 2017 15:53:04 GMT

    [ https://issues.apache.org/jira/browse/QPID-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998491#comment-15998491
] 

ASF subversion and git services commented on QPID-7763:
-------------------------------------------------------

Commit 9493668e842b595115864575916774145e4fa703 in qpid-broker-j's branch refs/heads/6.1.x
from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=9493668 ]

QPID-7763: Change flow to disk operational log messages


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


Mime
View raw message