[
https://issues.apache.org/jira/browse/ARTEMIS-3297?focusedWorklogId=597084&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-597084
]
ASF GitHub Bot logged work on ARTEMIS-3297:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/May/21 04:19
Start Date: 15/May/21 04:19
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #3580:
URL: https://github.com/apache/activemq-artemis/pull/3580#issuecomment-841597351
@michaelandrepearce that's happening on the JournalstorageManager::pageWrite
https://github.com/clebertsuconic/activemq-artemis/blob/backup-journal/artemis-server/src/main/java/org/apache/activemq/artemis/core/persistence/impl/journal/JournalStorageManager.java#L410-L427
I'm using the storeAddEvent, using the same record type as the Add Message
and addRef.
Basically if you recover a message from the "paging area" it will come back
to the journal.
(at least for now).
We could use the same to write to Paging.. or simply do the route to
whatever is the best at the time of recovering. But at this version this is
always coming back to the journal no matter where it came from.
--
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: 597084)
Time Spent: 7.5h (was: 7h 20m)
> Journal Retention Feature
> -------------------------
>
> Key: ARTEMIS-3297
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3297
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 2.17.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> We should keep historical backup of the journal data, and having tools to
> recover data in case of data loss.
>
> Data loss could mean by unbehaved client's (say you mistakenly acknowledged
> data and your code caused the message to disappear earlier), or even after
> eventual bugs on the broker.
>
> To activate the functionality, you have to specify journal-history-data on
> broker.xml.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
