activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1235) Support the ability to enable queue and address deletion when broker.xml changes
Date Mon, 19 Jun 2017 16:53:00 GMT


ASF GitHub Bot commented on ARTEMIS-1235:

Github user michaelandrepearce commented on the issue:
    > I can only reiterate that removing queues that have messages in my view is a bad
thing and we shouldn't allow it. At least not without any thought as to what we should do
with the messages.
    I think this is fair that this should be the default behaviour, but i think it should
be customisable, different users will want different behaviour (indeed we do).
    To facilitate this i suggest adding an optional extra setting (queue deletion policy)
then at the same address settings level to:
    "do not remove queue"
    "purge on delete"
    "drain to address"
    RE the persistence changing from the bindings journal.
    I would suggest that this could come later, if in understand right this would almost be
a breaking release change as such a big 3.0 release, this PR i think could hold for the interim
to avoid having to make a breaking release, but support the use case.

> Support the ability to enable queue and address deletion when broker.xml changes
> --------------------------------------------------------------------------------
>                 Key: ARTEMIS-1235
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Michael Andre Pearce
> Currently on config reload, as per:
> Once the configuration file is changed (broker.xml) the following modules will be reloaded
> 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
> 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

View raw message