[rabbitmq-discuss] Federation Configuration and Duplicate Messages
Letourneau, John P (John)
john.letourneau at alcatel-lucent.com
Tue Jan 3 15:01:04 GMT 2012
First a compliment - this software is great how it just works out of the box! I know it has taken you all a while to get it there, but it is much appreciated by newbies like myself.
In my research I have a need for federating several brokers together. So I have some experiments I have been doing to learn the ins and outs of how it all works. For now I have 3 systems each with 1 broker. The idea is this represents a hierarchy that is 3 deep [not very broad at the moment 8-) ]. In my experiments I am wanting a "shared bus" for logging. This means that for clients on any machine, messages to the federated log exchange will be seen on all other machines, including itself. As one might expect, this sometimes results in the message being seen >1 time at some clients.
I played around with the hop count, but that did not really solve any problems other than eventually stopping the forwarding of a given message...as it should. So I am starting to think of alternative configurations that can give me the behavior of 1 msg to a client, distributing the message to all nodes in the network, be efficient of course, and also minimize the knowledge required at each of the nodes/clients so as to allow easy administration as the network grows. I would hate to have to be reconfiguring existing clients and brokers each time a new node is added to grow the overall network.
I have thought of introducing 'flow-up' exchanges and other means of directing the flow up/down the tree...these mental gynastics lead me to duplicate messages or too much topology information being needed. I also considered routing rules where perhaps the node name is used as the first word in the route [node2.log.critical]...to work I would define an exchange/queue binding that did a match on everything EXCEPT my node. Alas I could not find anything that allowed 'not' matching part of a route. It is also likely that we may not settle on a tree hierarchy but may allow a graph so as to allow path duplication; but that decision is still open.
I've looked through all posts since June 22 to see what others are encountering with federation...sadly not too many people seem to be using it. So, is there any hope for me?
Thanks in advance...
John Letourneau, DMTS topgun at bell-labs.com
Applications Research Domain
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss