[
https://issues.apache.org/jira/browse/ARTEMIS-4941?focusedWorklogId=926898&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-926898
]
ASF GitHub Bot logged work on ARTEMIS-4941:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jul/24 16:25
Start Date: 22/Jul/24 16:25
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #5108:
URL: https://github.com/apache/activemq-artemis/pull/5108
(no comment)
Issue Time Tracking
-------------------
Worklog Id: (was: 926898)
Remaining Estimate: 0h
Time Spent: 10m
> Remove update estimate after ARTEMIS-3067
> -----------------------------------------
>
> Key: ARTEMIS-4941
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4941
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Since the new paging model, where we don't keep paged messages for long as we
> used to keep, I'm going to remove the lazy application properties update done
> per ARTEMIS-3067.
> Say a message is updated after decoded for whatever reason, it gets difficult
> to trace back to its original calculations.
> I had already had issues in mirroring, and now it turns out that if you send
> a message in AMQP and receive with Core, and paging is involved the
> calculation will never return to 0 because the sizing might have been
> updated. and it's fairly difficult to trace back to when the message is going
> to leave the VM as it could still be referenced.
> ARTEMIS-3067 alleviated some consequences of the page cache we used to have
> with the older model, but with the newer model this should not be an issue
> any longer. The remedy is having more consequences than intended anyways.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
