Missing federated binding.
Fredrik Sörensson (Fredrik Sorensson/STO/Fritidsresor)
Hello.
We had a situation where a binding disappeared, and I wonder if there are any tips on what could be the reason?
The upstreams QM is a v2.8.7 (which is to be updated to 3.3.latest as soon as possible) and downstreams QM is a v3.3.0. On both QMs, two Headers exchanges are created (we create one Exchange per Information type). On the downstreams QMs, bindings are created to local queues. In the Admin GUI on the upstreams QM, I can see the federation of the exchanges.
However, we recently discovered that one of the bindings is missing. The local binding, the policies and connections are ok on the downstreams QM, but on the upstreams QM there is no federation exchange for one of the exchanges. I can’t view the bindings on the exchange on the upstreams QM since the GUI crashes. However, recreating the binding on the downstreams QM reinstated the upstreams federated exchange and it seems to work fine now.
I will ask the application team to prioritize upgrading the old QM instance. But until that can be completed, is there anything I can do to make this not happen again? Is this a well-known issue with 2.8.x <-> 3.3.x interoperability and the federation plugin? Do you have any hints for what I can look for in the log files that could explain what and why this happened?
/Fredrik Sörensson
Fredrik Sörensson (Fredrik Sorensson/STO/Fritidsresor)
Hello.
Continuing my own email thread here. I’ve searched the log files and I found this among other errors:
=ERROR REPORT==== 11-Jun-2014::09:01:31 ===
connection <0.2945.77>, channel 1 - error:
{amqp_error,command_invalid,"unknown exchange type 'x-federation-upstream'",
'exchange.declare'}
Which mirrors this email thread: http://markmail.org/message/qt3b7twsvxqyuaie That sounds similar to what I am experiencing, the versions are similar. I have checked, federation is definitely enabled on the QM, as it is used for other bindings.
Did you find out what the cause of the above error was, and was it fixed in later versions?
/Fredrik
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
rabbitmq-user...@googlegroups.com.
To post to this group, send email to
rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Simon MacMullen
> Hello.
>
> Continuing my own email thread here. I’ve searched the log files and I
> found this among other errors:
>
> =ERROR REPORT==== 11-Jun-2014::09:01:31 ===
>
> connection <0.2945.77>, channel 1 - error:
>
> {amqp_error,command_invalid,"unknown exchange type 'x-federation-upstream'",
> 'exchange.declare'}
>
> Which mirrors this email thread:
> http://markmail.org/message/qt3b7twsvxqyuaie That sounds similar to
> what I am experiencing, the versions are similar.
as a helper in 3.0.0, but it's used in the upstream. 3.x federation will
attempt to declare such an exchange upstream, but if the declare fails
(if they are talking to a 2.x broker or a 3.x broker with federation not
enabled) the declare will fail and they will declare a (less efficient)
fanout exchange instead.
> I have checked,
> federation is definitely enabled on the QM, as it is used for other
> bindings.
>
> Did you find out what the cause of the above error was, and was it fixed
> in later versions?
As to your original issue: are you saying the intermediate exchange
(named "federation: ..." vanished? That should not happen; could someone
have deleted it by mistake?
In general federation should be interoperable between 2.8.x and 3.3.x.
Cheers, Simon
>
> /Fredrik
>
> *From:*rabbitm...@googlegroups.com
> [mailto:rabbitm...@googlegroups.com] *On Behalf Of *Fredrik
> Sörensson (Fredrik Sorensson/STO/Fritidsresor)
> *Sent:* den 13 augusti 2014 16:02
> *To:* rabbitm...@googlegroups.com
> *Subject:* [rabbitmq-users] Missing federated binding.
> You received this message because you are subscribed to the Google
> Groups "rabbitmq-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to rabbitmq-user...@googlegroups.com
Fredrik Sörensson (Fredrik Sorensson/STO/Fritidsresor)
Yes, that is correct, the intermediate exchange vanished. But I don't think that anyone would delete it manually. It is a production environment so people are generally very cautious.
The intermediate exchanges do have to AutoDelete flag set, but I don't know what situation could trigger it to be used, as long as the binding still exists on the downstreams QM.
/Fredrik
To post to this group, send an email to rabbitm...@googlegroups.com.