[
https://issues.apache.org/jira/browse/ARTEMIS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054140#comment-16054140
]
ASF GitHub Bot commented on ARTEMIS-1235:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1345
@andytaylor
re:
> My opinion removing queues should never be done automatically even if
that is a configured flag.
We actually would want to automatically remove the queue still when using
tools like puppet/chef.
Use case we need this for is that a durable subscription is being decom'd
the app would need to be deployed (or underplayed) with the subscription gone,
after which we remove the queue for that subscription.
In this case there maybe build up of messages as message produce flow
continues and other subscriptions (queues) would still exist. As such we'd want
the queue removed still even if outstanding messages to deliver.
Re: Removing bindings journal
where would you put auto-created queues in this scenario, as we would only
control in puppet persistent/durable queues typically. as such couldn't have
these written to this file else puppet/chef would re-push the config file and
remove the auto-created queues created for non-durable topic consumers.
> Support the ability to enable queue and address deletion when broker.xml
> changes
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-1235
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1235
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Michael Andre Pearce
>
> Currently on config reload, as per:
> https://activemq.apache.org/artemis/docs/2.1.0/config-reload.html
> Once the configuration file is changed (broker.xml) the following modules
> will be reloaded automatically:
> Address Settings
> Security Settings
> Diverts
> Addresses & queues
> Notice: Address & queues won't be removed upon reload, given the risk of
> losing messages. You may execute explicit CLI or Management operations to
> remove destinations.
> Where an organisation uses tools like puppet or chef and need to fully change
> manage the broker they need an ability to delete queues and topics also via
> the config, as these tools control state of systems by config. Like wise in
> these scenario's where such tools are used to control state of a system
> typically an organisation will have controls and pre-prod environments where
> they push config through the environments as such risk of issue is removed re
> data loss / or accepted risk, as would have been pre-validated in
> non-ciritical non-prod envs.
> The default behaviour should be as is today (e.g. delete still doesn't
> occur), but an optional toggle so that queue's and address's are sync'd
> removed inline with the broker xml.
> Ideally it should be possible to toggle this ability by address pattern so if
> some address's you don't wish controlled this way and others you do, this
> should be possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
