[collectd] zeormq architecture inquiry
allanfeid at gmail.com
Mon Aug 29 18:54:13 CEST 2011
Thanks Francois, the way the code is right now, the subscriber is the node
doing the bind, and the publisher connects to the subscriber. This would
mean that your central collectd process would be able to do the filtering
since it is the subscriber.
As far as AMQP goes, we have noticed scaling problems with the broker model,
where this box becomes complex to scale out and seems to be the bottle neck.
That is why ZeroMQ is appealing for this kind of situation.
On Mon, Aug 29, 2011 at 12:42 PM, Francois-Xavier Bourlet
<fx at dotcloud.com>wrote:
> Hi guys,
> Just a little note: The current implementation of ZMQ filter on the
> subscriber, not on the publisher...
> Seem that ZMQ v3 is addressing the problem.
> my 2cents
> On Mon, Aug 29, 2011 at 9:22 AM, Florian Forster <octo at collectd.org>wrote:
>> Hi Allan,
>> if you're after distributing the load, you might want to take a look at
>> the AMQP plugin, too. It has these "topic" branches, where subscribers
>> can subscribe to "matching" messages only. This allows you to distribute
>> the load in a consistent manner and is re-configurable during runtime.
>> It's possible to only subscribe to certain messages in ZeroMQ as well,
>> but I *think* they match the message content for this. Since the plugin
>> uses the binary protocol, that might not work for us. I might be wrong,
>> though, and there is some "label" that you can attach to messages, which
>> would make this kind of filtering possible with ZeroMQ, too.
>> Florian octo Forster
>> Hacker in training
>> GnuPG: 0x0C705A15
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (GNU/Linux)
>> -----END PGP SIGNATURE-----
>> collectd mailing list
>> collectd at verplant.org
> François-Xavier Bourlet
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the collectd