You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/06/20 14:24:00 UTC

[jira] [Updated] (QPID-7791) Recover metadata into direct memory

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

Keith Wall updated QPID-7791:
-----------------------------
    Fix Version/s: qpid-java-6.0.8
                   qpid-java-6.1.4

> Recover metadata into direct memory
> -----------------------------------
>
>                 Key: QPID-7791
>                 URL: https://issues.apache.org/jira/browse/QPID-7791
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>             Fix For: qpid-java-broker-7.0.0, qpid-java-6.1.4, qpid-java-6.0.8
>
>
> Currently, the message store on reading of the metadata creates heap buffers rather than direct.  This code path is used by both recovery and re-reading metadata following a flow to disk.
> This approach means that the Broker footprint differ:  If messages come in on the wire, content and metadata (at least initially, is in direct), if messages are recovered, metadata is in heap.   This makes giving advice around the size of Qpid's memory more difficult.   If the user makes poor choice a situation is possible where the Broker may not be restartable because there is too little heap to recover all the metadata.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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