You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2022/01/20 13:57:00 UTC
[jira] [Reopened] (ARTEMIS-3021) OOM due to wrong CORE clustered message memory estimation
[ https://issues.apache.org/jira/browse/ARTEMIS-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reopened ARTEMIS-3021:
-------------------------------------
> OOM due to wrong CORE clustered message memory estimation
> ---------------------------------------------------------
>
> Key: ARTEMIS-3021
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3021
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Fix For: 2.20.0
>
> Time Spent: 6h
> Remaining Estimate: 0h
>
> This is affecting clustered Core messages (persistent or not).
> The process that cause the wrong estimation is:
> # add route information to the message
> # get memory estimation for paging (ie address size estimation) without accounting the new route information
> # get message persist size for durable append on journal/to update queue statistics, triggering a re-encoding
> # re-encoding (can) enlarge the message buffer to be the next power of 2 available capacity
> The 2 fixes are:
> * getting a correct memory estimation of the message (including the added route information)
> * save an excessive buffer growth caused by the default Netty's ByteBuf::ensureWritable strategy
--
This message was sent by Atlassian Jira
(v8.20.1#820001)