[
https://issues.apache.org/jira/browse/ARTEMIS-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Nigro updated ARTEMIS-3021:
-------------------------------------
Description:
Durable CORE messages with clustering can get their internal buffer enlarged by
encodeHeadersAndProperties while being persisted on the journal, but the
address size memory estimation using the estimated memory of a message is
performed before that, making it less precise.
This bad timing estimation, together with Netty ByteBuf auto-sizing mechanism
can cause the broker to underestimate the message footprint, causing it to go
OOM.
was:
Durable CORE messages can get their internal buffer enlarged by
encodeHeadersAndProperties while being persisted on the journal, but the
address size memory estimation using the estimated memory of a message is
performed before that, making it less precise.
This bad timing estimation, together with Netty ByteBuf auto-sizing mechanism
can cause the broker to underestimate the message footprint, causing it to go
OOM.
> OOM due to wrong CORE 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: 1h 40m
> Remaining Estimate: 0h
>
> Durable CORE messages with clustering can get their internal buffer enlarged
> by encodeHeadersAndProperties while being persisted on the journal, but the
> address size memory estimation using the estimated memory of a message is
> performed before that, making it less precise.
> This bad timing estimation, together with Netty ByteBuf auto-sizing mechanism
> can cause the broker to underestimate the message footprint, causing it to go
> OOM.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
