[rabbitmq-discuss] federation Issues

[Simon MacMullen]

On 27/06/14 00:27, Ganann, Kale wrote:
> We just upgraded from 3.2.1 to 3.3.4 and federation died on us.  Looking
> at the cluster, it appears some... overenthusiastic dev renamed the
> cluster

That should not be a problem.

 From 3.2.x to 3.3.x we changed from having the federation plugin give 
the cluster a name through the local_nodename parameter, to having a 
broker-wide cluster name that can be used by the federation plugin.

But the cluster name doesn't matter that much. It's used to name the 
queues which federation uses internally, and it shows up in transmitted 
bindings and messages so the plugin (and sysadmins) know where message 
have been. But it's not something you should have to get "correct" for 
things to work - there's no correct value.

> and now when federation creates new linkages, it creates them
> as clustername:vHost:queue, rather than usertoken:vHost:queue.

I really do not understand any of this.

What do you mean by "linkages"? Bindings? Federation links (as shown in 
the status)? Something else?

Also, what do you mean by usertoken?

> Also, on
> the federation upstreams, the parameter field seems to have vanished, so
> I can't update the user tokens for specific vHosts.

I guess you are saying something about the local_username or 
local_nodename fields here? local_username is gone, there is no need to 
configure it at all any more. local_nodename is replaced by the cluster 
name.

> I've been going
> through the patch notes - is this intentional, or is something else
> going on?

The removal of local_username and local_nodename was intentional.

> And can I just remove the cluster name?

Clusters always have a name.

>  I've tried deleting
> the old dynamically created fed stuff so that it gets recreated, but the
> new stuff just doesn't seem to work.  Any help is appreciated.

What does the link status look like?

Cheers, Simon

-- 
Simon MacMullen
RabbitMQ, Pivotal