[rabbitmq-discuss] Federated Cluster Issue
richard at raseley.com
Wed Apr 24 23:54:52 BST 2013
Thank you - that error in the URI was the results at my attempts at
obfuscation. I am indeed referencing the vhost on the remote cluster.
Could you clarify this remark: "you will not actually see the links until
the exchanges you are federating actually exist on the upstream host"?
I ask because based on my understanding is that the URI defines the remote
system, username, password, and vhost - while the policy defines the local
exchange to be associated with the link. Am I misunderstanding this (e.g.
is the policy actually defining the remote exchange to be federated in a
On Tue, Apr 23, 2013 at 6:32 AM, Chris <stuff at moesel.net> wrote:
> On Mon, Apr 22, 2013 at 6:11 PM, Richard Raseley <richard at raseley.com>wrote:
>> 3) Added a new upstream on each cluster pointing to the other with a URI
>> that looks similar to the following (from the perspective of "cluster-01":
>> amqp://user:[email protected]/cluster02.exchange
> You might also want to double-check the url you are using to setup the
> federation-upstream. The URL above corresponds to a *virtual host* called
> "cluster02.exchange". Is this what you really intended? If you are
> actually using the default virtual host, then you should just use
> amqp://user:[email protected]/ and setup policies for the
> exchanges you wish to federate (as in your step 4).
> One other thing to note-- you will not actually see the links until the
> exchanges you are federating actually exist on the upstream host. So if
> you haven't yet created the exchanges, you'll want to do that too.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss