[jira] [Closed] (ARTEMIS-2462) Allow store and forward queue to be deleted after scaledown

["clebert suconic (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

clebert suconic closed ARTEMIS-2462.
------------------------------------
    Resolution: Fixed

> Allow store and forward queue to be deleted after scaledown
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-2462
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2462
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.10.0
>            Reporter: Howard Gao
>            Assignee: clebert suconic
>            Priority: Major
>             Fix For: 2.11.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> After a node is scaled down to a target node, the sf queue in the target node is not deleted (the sf queue takes the form of $.artemis.internal.sf.<cluster-name>.<nodeid>).
> Normally this is fine because maybe reused when the scaled down node is back up.
> However in Openshift/Kubernetes environment many drainer pod (scale down broker) can be created and then shutdown in order to drain the messages to a live node (pod). Each drainer pod will have a different node-id. Over time the sf queues in the target broker node grows and those sf queues are no longer reused.
> Although use can use management API/console to manually delete them, it would be nice to have an option to automatically delete those sf queue/address resources after scale down.
> One option (my proposal) is define a system property on the scale down broker.
> If the property is "true" the broker will send a message to the target broker signalling that the SF queue is no longer needed and should be deleted.
> If the property is not defined (default) or other values then "true", the scale down won't remove the sf queue (current behavior).
> This solution could well be suitable for openshift/kubernetes environment because we can easily pass any environment variable into the image to enable/disable this feature.
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)