mirror of
https://github.com/apache/activemq-artemis.git
synced 2025-02-07 02:29:08 +00:00
85b2f4b126
This commit does the following:
- Replaces non-inclusive terms (e.g. master, slave, etc.) in the
source, docs, & configuration.
- Supports previous configuration elements, but logs when old elements
are used.
- Provides migration documentation.
- Updates XSD with new config elements and simplifies by combining some
overlapping complexTypes.
- Removes ambiguous "live" language that's used with regard to high
availability.
- Standardizes use of "primary," "backup," "active," & "passive" as
nomenclature to describe both configuration & runtime state for high
availability.
55 lines
2.5 KiB
Plaintext
55 lines
2.5 KiB
Plaintext
= Data Retention
|
|
:idprefix:
|
|
:idseparator: -
|
|
|
|
If you enable `journal-retention` on broker.xml, ActiveMQ Artemis will keep copy of every data that has passed through the broker on this folder.
|
|
|
|
[,xml]
|
|
----
|
|
...
|
|
<journal-retention unit="DAYS" directory="history" period="365" storage-limit="10G"/>
|
|
...
|
|
----
|
|
|
|
ActiveMQ Artemis will keep a copy of each generated journal file, up to the configured retention period, at the unit chose.
|
|
On the example above the system would keep all the journal files up to 365 days.
|
|
|
|
It is also possible to limit the number of files kept on the retention directory.
|
|
You can keep a storage-limit, and the system will start removing older files when you have more files than the configured storage limit.
|
|
|
|
Notice the storage limit is optional however you need to be careful to not run out of disk space at the retention folder or the broker might be shutdown because of a critical IO failure.
|
|
|
|
You can use the CLI tools to inspect and recover data from the history, by just passing the journal folder being the retention directory.
|
|
|
|
Example:
|
|
|
|
[,shell]
|
|
----
|
|
./artemis data print --journal ../data/history
|
|
----
|
|
|
|
==== Paging and Large Messages
|
|
When retention is enabled, paging and large messages are also stored on the retention folder for replaying, so replay will also work for both paged and large messages.
|
|
|
|
==== Non Persistent Messages
|
|
Non persistent messages are never stored anywhere in the broker. If you intend to retain data your producers should be using Durable messages.
|
|
|
|
== Recovering data from retention
|
|
|
|
To recover data from the retention folder, you can use the method link:https://activemq.apache.org/components/artemis/documentation/javadocs/javadoc-latest/org/apache/activemq/artemis/api/core/management/ActiveMQServerControl.html#replay(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String)[replay] on the management console:
|
|
|
|
image::images/replay-method.png[align="center"]
|
|
|
|
The broker will scan the set of files accordingly to the parameters you passed and it will send these methods to a target queue that you selected.
|
|
|
|
=== CLI recover operation
|
|
|
|
The CLI recover operation is intended as a low level operation, where data is read and recovered directly into a set of journal files.
|
|
Notice uou should never manipulate journal files that are being used by an active broker as that could risk the integrity of your data files and running broker.
|
|
|
|
[,shell]
|
|
----
|
|
./artemis data recovery --journal ../data/history --target ../data/recovered --large-messages ../data/large-messages
|
|
----
|
|
|