Of course that solution won't work as you can't send from workers to a LoadBalancer sub queue.
Another solution would be to move messages to an awiatingWorkers subqueue and read from there when assigning messages to workers. On May 5, 11:43 am, philip <[email protected]> wrote: > When the loadbalancer is flooded with a high number of messages it can > get into a position where it cannot deal with the messages as quickly > as the messages are arriving, leading to overall badness. This is > because the loadbalancer has to read through the entire queue of > messages to find the ReadyToWork messages from the workers, which when > the queue is big can take a while. > > One possible fix might be to get the workers to send their ReadyToWork > messages to a subqueue and get the loadbalancer to watch the subqueue. > This way the loadbalancer should be able to deal out a message nearly > as soon as the ReadyToWork message arrives. > > -- > 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 > athttp://groups.google.com/group/rhino-tools-dev?hl=en. -- 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.
