Description
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.
Attachments
Issue Links
- incorporates
-
ARTEMIS-2485 Deleting SNF Queue should also delete associated remote bindings
-
- Closed
-
- links to
