You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@activemq.apache.org by GitBox <gi...@apache.org> on 2019/08/27 14:38:12 UTC

[GitHub] [activemq-artemis] gaohoward opened a new pull request #2813: ARTEMIS-2462 Allow store-forward queue to be deleted afte scaledown

gaohoward opened a new pull request #2813: ARTEMIS-2462 Allow store-forward queue to be deleted afte scaledown
URL: https://github.com/apache/activemq-artemis/pull/2813
 
 
   After a node is scaled down to a target node, the sf queue in the
   target node is not deleted.
   
   Normally this is fine because may be reused when the scaled down
   node is back up.
   
   However in cloud environment many drainer pods 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.
   
   In this PR it defines 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
   than "true", the scale down won't remove the sf queue.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services