On 01/26/2012 02:02 PM, Bryan Thompson wrote:
> Ok.
> 
> Not sure if this matters to your proposal, but GROUP is not always a
> single name/value pair.  There can be multiple GROUPs for a metadata
> record.

If there is more than one value for GROUP it could be an array instead
of a string, That'd bump the efficiency a bit higher on that case, but
cost a few bytes for the regular "one or none" case.

> 
> Is gmetad really pulling the XML from gmond?  Why not just embed the
> logic to listen for UDP packets and develop a soft state model of the
> cluster metrics in gmetad?  Jeff, is that what you meant by a major
> rewrite of gmetad?
> 

Yeah gmetad hits each "source" to collect data, the source in this case
is the tcp listener port of gmond, which only knows how to spew a full
xml state table.

I'm personally in favor of entirely killing off gmetad in favor of a
more extensible gmond. If you could bolt on a storage, transport, or
query plugin as easily as you could a metric module it'd be completely
killer.

-Dave

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to