[jira] [Updated] (ARTEMIS-4065) Option to use non persistent counters in paging. Rebuild them upon start if persistence is disabled on them

["Clebert Suconic (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic updated ARTEMIS-4065:
-------------------------------------
      Component/s: Broker
    Fix Version/s: 2.28.0

> Option to use non persistent counters in paging. Rebuild them upon start if persistence is disabled on them
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4065
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4065
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Clebert Suconic
>            Priority: Major
>             Fix For: 2.28.0
>
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Instead of storing records on journal for counting how many records there are in paging, the system should instead just swipe the paging system in parallel with processing data.
> The changes I'm making will take a snapshot of the current records of paging, 
> and then it will read all the pages to rebuild the counters.
> On tests I am making from a real data server, a system that had a lot of pages (700) needed less than 1 minute to rebuild the counters, and the messages were available to be delivered while the swipe was being done.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)