Hi Eric, FYI: The 'sources' and 'destinations' configuration fields both accept a list. The shovel plugin doesn't actually pull/push to/from all of these simultaneously, it uses them as a form of simple failover - if a connection fails, it uses the next one in the list.
It sounds like for your scenario (when clustering in general), it would be easier to use the federation plugin (http://www.rabbitmq.com/federation.html). When you declare a federated exchange on the downstream/master cluster, the plugin auto-magically declares queues (mirrored if configured) on the upstream/AWS cluster .. you would then bind a mirrored queue to the federated exchange on the downstream/master cluster to cause messages to be routed across the link to that queue. The plugin will then stay connected even if one of your nodes on either cluster go down .. if the whole downstream/master cluster goes away/down, then messages will pile up in the upstream/AWS queues, and be transfered once the link is re-established. Does that solve your use-case? Regards, Brendan On Thu, Jun 28, 2012 at 11:11 PM, Eric <[email protected]> wrote: > I have a question about configuring shovel for my application. We > currently have two broker clusters that are separated by a network > partition; one cluster of two brokers in AWS, and another cluster of two > brokers in a separate network environment. The non-AWS cluster is the > "master", so we want to shovel items from the AWS cluster to the master. > > The shovel configuration allows for multiple source brokers, but if I want > redundant shovels running, how should I set them up? Should I create a > shovel in each of the clustered AWS brokers that is configured to connect > only to the broker its installed on, create a non-mirrored queue for that > shovel to consume, and bind it only to the local exchange? Or should I be > trying to configure each shovel to declare a mirrored queue and connect to > each broker? It seems like the latter would cause every message to be > published twice. > > > _______________________________________________ > rabbitmq-discuss mailing list > [email protected] > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss > > -- You received this message because you are subscribed to the Google Groups "rabbitmq-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rabbitmq-discuss?hl=en.
