[
https://issues.apache.org/jira/browse/ARTEMIS-3297?focusedWorklogId=596879&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-596879
]
ASF GitHub Bot logged work on ARTEMIS-3297:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/May/21 20:04
Start Date: 14/May/21 20:04
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on a change in pull request
#3580:
URL: https://github.com/apache/activemq-artemis/pull/3580#discussion_r632767871
##########
File path: artemis-server/src/test/resources/ConfigurationTest-full-config.xml
##########
@@ -406,6 +406,9 @@
<page-max-concurrent-io>17</page-max-concurrent-io>
<read-whole-page>true</read-whole-page>
<journal-directory>somedir2</journal-directory>
+ <journal-history-directory>history</journal-history-directory>
Review comment:
@michaelandrepearce some time ago, I talked to an Architect at my job
who wanted to get diffs from the broker and send over to another site from time
to time.
This kind of feature would be useful for such case maybe?
It wouldn't hurt to have it though.. it's just an additional option.
I am thinking to have a commented out xml on the broker.xml that will have 7
days, 10G as the config. So if users just uncomment that they will have the 7
days and 10G max disk.
--
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: 596879)
Time Spent: 3h 10m (was: 3h)
> Historical Backup of Broker Data
> --------------------------------
>
> 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: 3h 10m
> 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)
