[
https://issues.apache.org/jira/browse/WHIRR-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149724#comment-13149724
]
Andrei Savu commented on WHIRR-396:
-----------------------------------
+1 integration test also passing on cloudservers-uk.
> service/ganglia needs non-zero send_metadata_interval= in gmond.conf
> --------------------------------------------------------------------
>
> Key: WHIRR-396
> URL: https://issues.apache.org/jira/browse/WHIRR-396
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.6.0
> Environment: EC2
> Reporter: Paul Baclace
> Attachments: WHIRR-396.patch
>
>
> 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 ]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
