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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot logged work on ARTEMIS-3021:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Dec/21 06:17
            Start Date: 01/Dec/21 06:17
    Worklog Time Spent: 10m 
      Work Description: franz1981 commented on pull request #3370:
URL: https://github.com/apache/activemq-artemis/pull/3370#issuecomment-983325073


   Given that CI is green and I got reviewed by @clebertsuconic about it, I think this is ready to go...merging soon today if none complain :+1: 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 688439)
    Time Spent: 5h 50m  (was: 5h 40m)

> 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)