[jira] [Commented] (ARTEMIS-3021) OOM due to wrong CORE clustered message memory estimation

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451655#comment-17451655 ] 

ASF subversion and git services commented on ARTEMIS-3021:
----------------------------------------------------------

Commit ad4f6a133af9130f206a78e43ad387d4e3ee5f8f in activemq-artemis's branch refs/heads/main from franz1981
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ad4f6a1 ]

ARTEMIS-3021 OOM due to wrong CORE clustered message memory estimation


> 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
>          Time Spent: 5h 50m
>  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)