On Tue, Jun 30, 2015 at 7:46 PM, Kalyan Bade <[email protected]> wrote:
> Isn't the current node need to know who are all part of the multicast group > in order for SHOUT to be reliably transferred to all members? There is no "all" and no "reliably"... nodes broadcast JOIN messages, and every node maintains its own vision of what groups exist. With pauses and handshaking you can be more or less sure of membership. > We did play around with different sleep values just before sending the > SHOUT. It has become less prevalent with higher sleep values. But, I was > looking for a deterministic solution as we are seeing the issue rarely with > a sleep as high as 10 seconds That is abnormal for inproc; you'd expect everything to be settled in a second at most. You may have some other issues slowing down thread startup. > Btw, is gossip network not mandatory for forming the zyre mesh network? Over WiFi or Ethernet you'd use beaconing to start with, and gossip if you have a larger network and you want to control discovery. Over inproc there's no alternative to gossip. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
