[
https://issues.apache.org/jira/browse/ARTEMIS-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854581#comment-17854581
]
Stephen Baker commented on ARTEMIS-2965:
----------------------------------------
Just a vote from me; we just hit an issue where the mirror was growing faster
than it was draining for an extended period of time and we caused a service
disruption, disabling the mirror in broker.xml and restarting. An official and
live way to do this would have helped.
> Allow mirror to stop capture events and delete inner queue
> ----------------------------------------------------------
>
> Key: ARTEMIS-2965
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2965
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.16.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Critical
>
> When a mirror starts, the current events will not be cleared when
> brokerConnection.stop() is called.
>
> We should support removing the Mirror manager, and deleting the queue upon
> brokerConnection.stop().
> (or another method TBD that would determine the semantic to remove the SnF
> queue and future generation on mirror).
> Related comments:
> [https://github.com/apache/activemq-artemis/pull/3316#discussion_r513491335]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
