Thanks! Am about to try and when I try to run receiver.rb getting below
error (https://devco.net/rip/mcollective-registration-receiver.rb)
/usr/lib/ruby/gems/1.8/gems/stomp-1.3.2/lib/stomp/connection.rb:284:in
`subscribe': a valid subscription id header is required
(Stomp::Error::SubscriptionRequiredError)
from /root/receiver.rb:21:in `initialize'
from /root/receiver.rb:91:in `new'
from /root/receiver.rb:91
Am using rabbitmq connector. Not sure why its not getting the subscription
id.
On Monday, August 29, 2016 at 8:23:46 PM UTC+5:30, R.I.Pienaar wrote:
>
>
>
> ----- Original Message -----
> > From: "rakare2015" <[email protected] <javascript:>>
> > To: "mcollective-users" <[email protected] <javascript:>>
> > 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 [email protected].
For more options, visit https://groups.google.com/d/optout.
