[ 
https://issues.apache.org/jira/browse/QPID-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-8168:
-----------------------------
    Fix Version/s: qpid-java-broker-7.1.0

> [Broker-J] Broker should flow to disk transient messages when heap usage 
> reaches critical threshold in order to avoid running of heap memory due to 
> consumption of heap by transient message metadata
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8168
>                 URL: https://issues.apache.org/jira/browse/QPID-8168
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, 
> qpid-java-broker-7.0.2, qpid-java-6.0.8, qpid-java-broker-7.0.0, 
> qpid-java-broker-7.0.1, qpid-java-broker-7.1.0
>            Reporter: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-7.1.0
>
>
> The flow to disk is currently triggered when direct memory usage reaches 
> predefined threshold ({{broker.flowToDiskThreshold}} which is set to 75% of 
> direct memory size by default). However, in some situations (for example, 
> when direct memory size is big and heap memory size is small), the direct 
> memory threshold is not reached but the heap is fully occupied by transient 
> messages data, the broker runs out of heap memory.
> The broker behaviour can be improved by triggering flow to disk when a heap 
> occupancy reaches the critical threshold in addition to direct memory usage 
> threshold.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to