Thanks Justin I understand that zyre cannot use beacon and gossip at the same time, but I need to allow my users to choose the discovery mecanism at runtime (some of them cannot use beacon), so I hoped both mecanism work equally well, but it seems that is it not yet the case.
Bruno On Thu, Aug 24, 2017 at 4:29 PM, Justin Azoff <justin.az...@gmail.com> wrote: > On Thu, Aug 24, 2017 at 8:52 AM, brunobodin . <brunobo...@gmail.com> > wrote: > > Hi all, > > > > I am still trying to deploy zyre using both gossip and UDP, and in gossip > > mode only, sometimes (like 1/10 of runs, no reliable way to reproduce > yet), > > with only 2 nodes, I get a kind of intinite loop : both > > nodes keeps sending enter/exit events to the other (although there is > only > > one call to start in each process). > > Zyre isn't really written to support both gossip and beacon. There > are a number of fixes that need to be made to enable the use of both > at the same time. Right now as soon as you turn on gossip it turns of > beacon. > > > Each node only performs a start and use the header of the enter event of > > other node for further configuration. > > > > Sounds like > > https://github.com/zeromq/czmq/issues/1697 > > and > > https://github.com/zeromq/czmq/issues/1689 > > I couldn't get gossip to work reliably, and in order for it to be > production ready it really needs TTL support. For me it was easier to > write my own discovery service > (https://github.com/JustinAzoff/simpledisco/blob/master/zsimpledisco.c) > than to fix gossip. It needs a REQUIRE PEER patch for zyre in order > to be used though, I have some pull requests I need to send over. > > -- > - Justin > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > https://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org https://lists.zeromq.org/mailman/listinfo/zeromq-dev
