RabbitMQ federation: filter/exclude topics to avoid cross-cluster bindings

[Roy]

Hi Team,

I have a RabbitMQ setup with three clusters: A, B, and C, all using the virtual host "vhost_a", which is federated among the clusters (using the "rabbitmq_federation" plugin). When I publish a message to the topic HELLO on "vhost_a" at Cluster B and subscribe to the same topic HELLO within Cluster B, I notice that unnecessary federation bindings are created from Clusters A and C for that topic, leading to overhead on those clusters. I am looking for ways to optimize my RabbitMQ federation configuration to avoid these unnecessary bindings. I want to ensure that only essential topics are federated without creating unnecessary cross-cluster bindings. Does anyone have any suggestions on how I can configure federation settings to include/exclude/filter topics?If necessary, here are some more details about the virtual host, exchange, and federation settings. The virtual host is configured with an exchange named "mqtt.topic" (type: topic) with the policy {"federation-upstream-set": "all"} applied to that exchange. The federation upstreams between clusters A, B, and C are set up using the parameters {"ack-mode":"no-ack","bind-nowait":true,"exchange":"mqtt.topic","max-hops":1,"trust-user-id":true,"uri":"amqp://<upstream_url>"}

Any guidance would be greatly appreciated.

Thanks

Roy