[WHIRR-396] service/ganglia needs non-zero send_metadata_interval= in gmond.conf

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: 0.7.0

Environment

EC2

• Assignee: Joris Bontje
• Reporter: Paul Baclace
• Created: 13/Oct/11 07:23
• Updated: 14/Nov/11 16:33
• Resolved: 14/Nov/11 16:33

Description

My tests of ganglia+hadoop+HBase on EC2 (aws-ec2) show intermittently missing charts for slave nodes. I suspect it is a timing issue and the Ganglia FAQ points out that send_metadata_interval should be 30-60, not zero, when unicast is used. This is set to 0 in 0.6.0 and changing it to 30 fixes the problem.

For multicast use, a non-zero value is not harmful and might increase startup sequence robustness there too.

Ganglia FAQ:
"In recent versions of gmond (3.1.x), a new global variable was added in gmond.conf called 'send_metadata_interval', with a default setting of 0. Purpose was to reduce network traffic. In 3.1 metric data is sent separately from metadata e.g. metadata contains detailed description, grouping, other possible setting. A value of zero means that the gmond will send metadata when it starts, and no other time (which is consistent with older versions of ganglia)."
[ http://sourceforge.net/apps/trac/ganglia/wiki/FAQ ]