----- Original Message ----- > From: "rakare2015" <rakare2...@gmail.com> > To: "mcollective-users" <mcollective-users@googlegroups.com> > Sent: Monday, 29 August, 2016 16:47:12 > Subject: Re: [mcollective-users] Registration monitor not receiving messages > properly in big infra
> I just > found > http://allanfeid.com/content/create-inventory-tool-using-mcollectives-registration-feature > which say to use queue instead of topic which is more comfortable to avoid > to load broker. Also I > found https://devco.net/rip/mcollective-registration-receiver.rb which is > service to received queue particularly for registration. Am just doing on > this and just want to know where the data will be stored by this receiver > service? > yes, using a queue deals with the main problem and the receiver you found helps it scale without it running inside a mcollective daemon - its basically a purpose built mco daemon. The receiver you found will send the messages one by one to a agent you provide called registration hosted inside the receiver, so you can decide what happens with it. This code is a bit ancient so probably needs some modernising for recent mcollectives but yes, this is the way to build a large scale registration service -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mcollective-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
