You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2018/04/20 09:40:00 UTC
[jira] [Created] (QPID-8168) [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
Alex Rudyy created QPID-8168:
--------------------------------
Summary: [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-broker-7.0.1, qpid-java-broker-7.0.0, qpid-java-6.0.8, qpid-java-broker-7.0.2, qpid-java-broker-7.0.3, qpid-java-6.1.6, qpid-java-broker-7.1.0
Reporter: Alex Rudyy
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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org