[
https://issues.apache.org/jira/browse/ARTEMIS-3297?focusedWorklogId=598372&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-598372
]
ASF GitHub Bot logged work on ARTEMIS-3297:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/May/21 00:15
Start Date: 18/May/21 00:15
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #3580:
URL: https://github.com/apache/activemq-artemis/pull/3580#issuecomment-842727677
@michaelpearce-gain it should be done after...
I'm renaming the file since the lock... but the actual copy should be done
outside of any locking.
there might be some tweaking to be done into it though. but that was my
intention at least.
--
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 598372)
Time Spent: 15h 50m (was: 15h 40m)
> 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: 15h 50m
> 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)
