[zeromq-dev] Extending pipeline model, distributing jobs based on the type of job to specific workers

Lindley French lindleyf at gmail.com
Mon Feb 17 09:01:11 CET 2014

This comes back to a suggestion I made a few weeks ago, that whether or not
a socket drops or blocks at HWM should be a socket option, not hard-coded.
In particular this is true for pub sockets.

IF this could be arranged at the very least for inproc pub sockets, even if
it weren't reasonable over a network, you could do:
1) Inproc pub of all jobs
2) Inproc sub per job type, then forward the job to a tcp push
3) TCP pull on the workers

However, this isn't how things work right now unfortunately.

On Mon, Feb 17, 2014 at 2:08 AM, aman mangal <mangalaman93 at gmail.com> wrote:

> Hi,
> I am trying to solve the following problem and I can't think of any model
> which I can use: I have n workers and 1 distributor. Distributor has jobs
> for n workers and every worker can solve only a specific type of job. It
> has to distribute jobs to the workers such that no job is dropped.
> I tried using pub-sub but it drops messages when the publisher queue is
> full. If I use pipeline model, it distributes jobs among all workers. Any
> addition to it would be really helpful. Dropping of a job is not fine
> compared to blocking the distributor, which is fine. I am a beginner in
> zeromq and have followed through the guide on the homepage.
> Thank you!
> Aman Mangal
> final year Undergraduate Student
> Department of Computer Science & Engineering
> IIT Bombay, India
> www.cse.iitb.ac.in/~amanmangal
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20140217/b14d6dfb/attachment.htm>

More information about the zeromq-dev mailing list