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 18:29:00 GMT


ASF GitHub Bot commented on ARTEMIS-1235:

Github user mtaylor commented on the issue:
    Having this policy driven seems to be the way to satisfy both requirements.  It also still
makes sense if we do go down the route of storing queues/addresses in config only (although
as @michaelandrepearce mentioned this will likely be an API break anyway).  
    @andytaylor @michaelandrepearce I don't think we need to implement all policies right
away, this can be user driven as and when requirements crop up.  The simplest thing right
now IMO is just to amend this commit to use something like:
    configDeleteQueue=[Off (Default), Force].
    And ensure the consequences of "Force"  are clearly documented.  
    @michaelandrepearce Given this is to become policy driven I can see more of a requirement
for this to be set at the address-settings level.

> 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