Simone,when the barista subscribes to something, he should use the load balancer address, not its own. all nodes behind a load balancer are identical. that is, it doesn't matter which node you get a message from, and it doesn't matter which node you get it from.
On Sun, Jun 7, 2009 at 8:57 PM, Simone Busoli <[email protected]>wrote: > Trying to wrap my head around it, nut successfully yet. I think I don't > grab the concept of load balancer completely yet.I mean, having the > configuration below: > > 1. messages named Starbucks.Messages.Cashier coming > from msmq://localhost/starbucks.cashier are load balanced (multiplexed) > among baristas? I guess so, but it's not what I observe with the > configuration below. It looks like baristas subscribe directly to the > cashier, therefore everyone receives a message when the cashier publishes > one. > What if two baristas subscribe to different messages coming from different > endpoints? Does the concept of load balancer still make sense? Wouldn't it > make more sense for the load balancer to tell which messages to subscribe > to, so that everyone load balanced through it receives them? > > 2. What route do messages published by baristas take? Are they > demultiplexed through the balancer? > > On Fri, Jun 5, 2009 at 15:26, Ayende Rahien <[email protected]> wrote: > >> That should work, yes.Can you take a look at the load balancer itself and >> see if it is doing what it is supposed to? >> It is supposed to cc to a current worker, only a single one. >> >> >> On Fri, Jun 5, 2009 at 6:45 AM, Simone Busoli <[email protected]>wrote: >> >>> BTW, here's what I did. >>> In Program.cs replaced the code for barista with: >>> >>> var barista1 = new RemoteAppDomainHost(typeof(BaristaBootStrapper)) >>> .Configuration("Barista1.config"); >>> barista1.Start(); >>> >>> var barista2 = new RemoteAppDomainHost(typeof(BaristaBootStrapper)) >>> .Configuration("Barista2.config"); >>> barista2.Start(); >>> >>> Removed Barista.config and added: >>> >>> Barista1.config: >>> >>> <bus threadCount="1" >>> loadBalancerEndpoint="msmq://localhost/starbucks.barista.balancer" >>> numberOfRetries="5" >>> endpoint="msmq://localhost/starbucks.barista1" >>> /> >>> <messages> >>> <add name="Starbucks.Messages.Cashier" >>> endpoint="msmq://localhost/starbucks.cashier"/> >>> </messages> >>> >>> Barista2.config: >>> >>> <bus threadCount="1" >>> loadBalancerEndpoint="msmq://localhost/starbucks.barista.balancer" >>> numberOfRetries="5" >>> endpoint="msmq://localhost/starbucks.barista2" >>> /> >>> <messages> >>> <add name="Starbucks.Messages.Cashier" >>> endpoint="msmq://localhost/starbucks.cashier"/> >>> </messages> >>> >>> >>> On Fri, Jun 5, 2009 at 12:39, Simone Busoli <[email protected]>wrote: >>> >>>> Any hint about where to look to figure out what's going on? >>>> >>>> >>>> On Fri, Jun 5, 2009 at 12:31, Ayende Rahien <[email protected]> wrote: >>>> >>>>> No, it is not supposed to do that. Only one message should be sent from >>>>> the LB >>>>> >>>>> >>>>> On Fri, Jun 5, 2009 at 5:05 AM, Simone Busoli <[email protected] >>>>> > wrote: >>>>> >>>>>> Some question about load balancing, I'm not sure I understand the >>>>>> concept completely.In the starbucks example the barista(s) uses a >>>>>> load balancer, so I suppose you can add another barista (using the same >>>>>> load >>>>>> balancer but with a different own endpoint) and everything would work as >>>>>> expected. For expected I mean that only one of them will prepare the >>>>>> drink, >>>>>> but trying it I see that each barista will prepare the drink >>>>>> instead, and the customer will receive two drinks. >>>>>> Is this what it's supposed to do? >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
