If you don't start more workers, and you're not blocked on hwms, each worker will get exactly one stop message. The sink can know what N is.
Pieter On Mar 4, 2013 6:58 PM, "Gerrit Hendrikus van Doorn" <[email protected]> wrote: > When sending N STOP messages through a pipeline, these messages might be > received at the SINK before the other messages have been processed by the > workers. > > Another (but not ideal) method is to have every worker send every message > to the SINK. The client, when finished, can publish (using a PUB socket) > the total number of messages it send to the SINK, which then counts the > number of received messages and exits when the total number is reached. > Before exiting it would notify the workers using another PUB/SUB > combination. > The downside of this construct is that every message that a worker > received has to be passed on to the SINK. > > - Gerrit > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
