Whirr
  1. Whirr
  2. WHIRR-396

service/ganglia needs non-zero send_metadata_interval= in gmond.conf

    Details

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

      EC2

      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 ]

      1. WHIRR-396.patch
        1 kB
        Joris Bontje

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Joris Bontje
            Reporter:
            Paul Baclace
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development