[
https://issues.apache.org/jira/browse/QPID-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057277#comment-16057277
]
Alex Rudyy commented on QPID-7791:
----------------------------------
As discussed, my only comment about the committed changes would be that we need
to dispose thread cached QpidByteBuffers on shutdown of the Asynchronous
recoverer executor and Configuration thread executor in order to maintain
correct direct memory usage statistics
> 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
> Assignee: 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: [email protected]
For additional commands, e-mail: [email protected]
