WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
On 23/04/12 20:47, theBuckWheat wrote:
> My application sends a work file out to one of several available remote
If the application does not need to designate a slave then work files
can go into a shared queue that all slaves subscribe to.
If your application must designate a slave then you could create a
dedicated queue for each slave.
> slaves. When the slave is done with the work, it posts a callback notice
> and stands by for the master to fetch the results file. When that file has
> been downloaded, after a little housekeeping, the slave can be put on the
> list of those available to send work.
> What is the best que structure to use with RabbitMQ to dispatch work to the
> pool of slaves? I have to manage the list of slaves because some might be
> close to their bandwidth limits, so it does not appear I can use the
> load-balance pattern.
It is not clear who is responsible for observing this constraint. If it
is the slave then it could take itself out of service. If it is the
application then you will need a separate queue per slave.