[
https://issues.apache.org/jira/browse/ARTEMIS-3759?focusedWorklogId=767188&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767188
]
ASF GitHub Bot logged work on ARTEMIS-3759:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/May/22 13:14
Start Date: 06/May/22 13:14
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #4054:
URL:
https://github.com/apache/activemq-artemis/pull/4054#issuecomment-1119604952
Just to be sure; you didnt have any concerns with the different
broker-connections bits having a completely different forms of governing
applicable addresses?
Issue Time Tracking
-------------------
Worklog Id: (was: 767188)
Time Spent: 3h 40m (was: 3.5h)
> Allow for Mirroring (Broker Connections) to specify a specific set of
> addresses to send events, as is done for a cluster connection
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3759
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3759
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: AMQP
> Affects Versions: 2.19.1, 2.21.0
> Reporter: Mikhail Lukyanov
> Priority: Major
> Attachments: ImageAddressSyntax.png, ImageInternalQueues.png
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> If a target broker of mirroring is in a cluster, then mirroring of the
> broker's internal queues also occurs, and often messages accumulate in such
> queues. In theory, internal cluster queues should not be mirrored, this does
> not make much sense.
> Therefore, it would be convenient to allow you to configure for which
> addresses and their queues mirroring will be performed, events will be sent
> (message-acknowledgements, queue-removal, queue-creation). The syntax that is
> used to specify the *_addresses_* of the *_cluster connection_* is well
> suited for this.
> Mirrored internal cluster queues
> !ImageInternalQueues.png!
> Address syntax
> !ImageAddressSyntax.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
