[
https://issues.apache.org/jira/browse/ARTEMIS-5573?focusedWorklogId=1013879&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1013879
]
ASF GitHub Bot logged work on ARTEMIS-5573:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Apr/26 21:53
Start Date: 07/Apr/26 21:53
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #6323:
URL: https://github.com/apache/artemis/pull/6323#issuecomment-4202422682
I added a commit to be squashed, returning the RELOAD state and persisting
the memory estimate on the storage (journal or paging).
I honestly don't think the scan will make any difference.. The real issue is
that the estimates were wrong in the first place...
But this commit should settle any discussion.
I think There are already version tests in the Version tests. but i will
make sure about it soon.
Issue Time Tracking
-------------------
Worklog Id: (was: 1013879)
Time Spent: 4h 20m (was: 4h 10m)
> Make AMQP Size immutable
> ------------------------
>
> Key: ARTEMIS-5573
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5573
> Project: Artemis
> Issue Type: Improvement
> Components: AMQP
> Affects Versions: 2.41.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> I have had a lot of issues, even recently on races between re-evaluating a
> message size in AMQP.
> Say a lazy decode happens at the wrong time and the memory estimates can be
> wrong.
> We have fixed issues along the years, but this is still a fragile process
> that is bound to fail. If an user for instance add a plugin breaking the
> chain of events.
> For that reason the memory estimate should already include enough estimation
> for any properties decoded and the process should be simplified.
> Less moving parts would mean less possibilities for bugs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
