397cef699a
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 added a boolean configuration parameter called cleanup-sf-queue to scale down policy so that if the parameter 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 parameter is not defined (default) or is "false" the scale down won't remove the sf queue. |
||
|---|---|---|
| .. | ||
| diagrams | ||
| hacking-guide/en | ||
| migration-guide/en | ||
| user-manual/en | ||