Jonathan Upthread, you said "if an instance of Rabbit goes offline under the current HA configuration, when it rejoins the cluster the queues are wiped clean" -- I am not sure if this is true?
Anyway why would you not just duplicate the message flows? I.e. set up two unclustered brokers. The producer sends everything to both brokers and considers a message processed only after both brokers confirm it. alexis On Sat, Nov 12, 2011 at 9:47 PM, Jonathan Oliver <[email protected]> wrote: > I'm just thinking of normal cloud-computing/distributed scenarios where any > instance may be transient and may go offline at any time for any reason. > Ideally when the instance comes back online (and the local storage isn't > transient/ephemeral), whatever was in the queue will still be there when it > rejoins the cluster. > _______________________________________________ > 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.
