I've tried to figure that out as well, and there is no way to do it on the ZMQ level. Have Task1 emit heartbeats and if Task2 and Task3 aren't seeing heartbeats, it means that the subscriptions haven't propagated yet. There can be a sizeable delay between subscribing and actually getting data (I've seen this as high as a few minutes, but I have a TON of subscribers in a complex topology).
On Thu, Aug 13, 2015 at 1:16 AM, Bachmair Florian - flexSolution GmbH < [email protected]> wrote: > Hello! > > Is there a way to determine the connection state of my subscriber? > > Szenario > > > Host1 Host2 > Task 1 > Task 2 Task3 > > > > Task 1 publishes a topic. > Task 2 and Task 3 are subscribing this topic > > Task 2 gets it, Task3 don't > > If I restart Task 3 it gets the value as well. > > > So is there a Oportunity to get the connection state of the subscriber > in Task3? > > _______________________________________________ > 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
