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

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

                Author: ASF GitHub Bot
            Created on: 21/Jan/21 09:34
            Start Date: 21/Jan/21 09:34
    Worklog Time Spent: 10m 
      Work Description: franz1981 commented on pull request #3370:
URL: https://github.com/apache/activemq-artemis/pull/3370#issuecomment-764505865


   the CI seems fine with this, so I'm just going to prepare a test for the 
specific change and we're ready to go 
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 538952)
    Time Spent: 2h 40m  (was: 2.5h)

> 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: 2h 40m
>  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
>  * save the buffer growth using the default Netty's ByteBuf::ensureWritable 
> strategy



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to