[
https://issues.apache.org/jira/browse/ARTEMIS-3297?focusedWorklogId=598334&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-598334
]
ASF GitHub Bot logged work on ARTEMIS-3297:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/May/21 23:20
Start Date: 17/May/21 23:20
Worklog Time Spent: 10m
Work Description: michaelpearce-gain edited a comment on pull request
#3580:
URL: https://github.com/apache/activemq-artemis/pull/3580#issuecomment-842705224
One more query, im trying to work out here, is the copy done whilst and
journal is blocked for write, or is it being done after like with compaction
and release not blocking the journal writes on the current file, but simply
before we do do the release or compaction, so journal writing to next file is
not blocked whilst we copy old one.
--
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: 598334)
Time Spent: 15h 40m (was: 15.5h)
> 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 40m
> 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)
