[zeromq-dev] A bit too reliable ;)

Daniel Krikun dkrikun0 at gmail.com
Sat Jan 10 20:42:24 CET 2015


I have a problem which seems to arise from zeromq reliability behaviors.
There is a master that spawns few processes which perform some tasks on its
behalf; eventually the master sends a message over PUSH socket (one for
each process) to shutdown itself. After some time the master can respawn
the processes and so on.
The problem emerges when one of the child processes crashes prematurely:
the master still sends the shutdown message, the child process receives it
and shuts down mistakenly.
While I can think of at least 2 solutions: timestamping (to detect an
obsolete message), or heartbeat (to avoid sending shutdown message to a
dead process), I thought, there must be a way for master to "reset" a
connection *before* spawning the child process in order to purge outgoing
I tried to close() a socket but that didn't help.

I'm using libzmq-2.2.0, TCP transport on a single Windows 7 x64 machine.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150110/fa17b4fd/attachment.htm>

More information about the zeromq-dev mailing list