[
https://issues.apache.org/jira/browse/ARTEMIS-3243?focusedWorklogId=616606&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-616606
]
ASF GitHub Bot logged work on ARTEMIS-3243:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jun/21 16:45
Start Date: 29/Jun/21 16:45
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on a change in pull request
#3633:
URL: https://github.com/apache/activemq-artemis/pull/3633#discussion_r660793210
##########
File path: docs/user-manual/en/amqp-broker-connections.md
##########
@@ -36,20 +39,115 @@ To define an AMQP broker connection, add an
`<amqp-connection>` element within t
*Notice:* If you disable auto-start on the broker connection, the start of the
broker connection will only happen after the management method
`startBrokerConnection(connectionName)` is called on the ServerController.
-*Important*: The target endpoint needs permission for all operations that you
configure. Therefore, If you are using a security manager, ensure that you
perform the configured operations as a user with sufficient permissions.
+*Important*: In addition to a matching mirror ID, the target endpoint needs
permission for all operations that you configure. Therefore, If you are using a
security manager, ensure that you perform the configured operations as a user
with sufficient permissions.
# AMQP Server Connection Operations
The following types of operations are supported on a AMQP server connection:
+* Mirrors
+ * The broker uses an AMQP connection to another broker and duplicate
messages and sends acknowledgements over the wire.
* Senders
* Messages received on specific queues are transferred to another endpoint
* Receivers
* The broker pulls messages from another endpoint
* Peers
* The broker creates both senders and receivers on another endpoint that
knows how to handle them. Currently, this is implemented by Apache Qpid
Dispatch.
-* Mirrors
- * The broker uses an AMQP connection to another broker and duplicate
messages and sends acknowledgements over the wire.
+## Mirrors
+The mirror option on the broker connection can capture events from the broker
and pass them over the wire to another broker. This enables you to capture
multiple asynchronous replicas. The following types of events are captured:
+
+* Message routing
+* Message acknowledgement
+* Queue and address creation
+* queue and address deletion
+
+When you configure a mirror, these events are captured from the broker, stored
on a local queue, and later forwarded to a target destination on another
ActiveMQ Artemis broker.
+
+To configure a mirror, you add a `<mirror>` element within the
`<amqp-connection>` element.
+
+The local queue is called `source-mirror-address`
+
+You can specify the following optional arguments.
+
+* `queue-removal`: Specifies whether a queue- or address-removal event is
sent. The default value is `true`.
+* `message-acknowledgements`: Specifies whether message acknowledgements are
sent. The default value is `true`.
+* `queue-creation`: Specifies whether a queue- or address-creation event is
sent. The default value is `true`.
+* `source-mirror-address`: By default, the mirror creates a non-durable
temporary queue to store messages before they are sent to the other broker. If
you define a name value for this property, an ANYCAST durable queue and address
is created with the specified name.
+
+An example of a mirror configuration is shown below:
+```xml
+<broker-connections source-mirror-id="1">
+ <amqp-connection uri="tcp://MY_HOST:MY_PORT" name="my-mirror">
+ <mirror queue-removal="true" queue-creation="true"
message-acknowledgements="true" source-mirror-address="myLocalSNFMirrorQueue"/>
+ <mirror target-mirror-id="2"/>
Review comment:
this will be removed.. docs are out of sync.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 616606)
Time Spent: 3.5h (was: 3h 20m)
> Enhance AMQP Mirror support with dual mirror
> --------------------------------------------
>
> Key: ARTEMIS-3243
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3243
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.17.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.18.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> at the current Mirror version, we can only mirror into a single direction.
> With this enhancement the two (or more brokers) would be connected to each
> other, each one having its own ID, and each one would send updates to the
> other broker.
> The outcome is that if you just transferred producers and consumers from one
> broker into the other, the fallback would be automatic and simple. No need to
> disable and enable mirror options.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
