FAQ
Ganglia metrics reporting is misconfigured
------------------------------------------

Key: HADOOP-1163
URL: https://issues.apache.org/jira/browse/HADOOP-1163
Project: Hadoop
Issue Type: Bug
Components: metrics
Affects Versions: 0.12.1
Environment: ganglia-3.0.3
Reporter: Michael Bieniosek
Priority: Minor


In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.

If I then get the gmond xml feed from the gmond server, I get this:

<METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
...
<METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>

Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

  • Michael Bieniosek (JIRA) at Mar 27, 2007 at 7:49 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484564 ]

    Michael Bieniosek commented on HADOOP-1163:
    -------------------------------------------

    My patch (I can't attach in the standard way since this issue is still open):

    --- src/java/org/apache/hadoop/metrics/ganglia/GangliaContext.java (revision 522712)
    +++ src/java/org/apache/hadoop/metrics/ganglia/GangliaContext.java (working copy)
    @@ -122,19 +122,6 @@
    public void emitRecord(String contextName, String recordName, OutputRecord outRec)
    throws IOException
    {
    -
    - // metric name formed from record name and tag values
    - StringBuffer nameBuf = new StringBuffer(recordName);
    - // for (String tagName : outRec.getTagNames()) {
    - Iterator tagIt = outRec.getTagNames().iterator();
    - while (tagIt.hasNext()) {
    - String tagName = (String) tagIt.next();
    - nameBuf.append('.');
    - nameBuf.append(outRec.getTag(tagName));
    - }
    - nameBuf.append('.');
    - String namePrefix = new String(nameBuf);
    -
    // emit each metric in turn
    // for (String metricName : outRec.getMetricNames()) {
    Iterator metricIt = outRec.getMetricNames().iterator();
    @@ -142,9 +129,8 @@
    String metricName = (String) metricIt.next();
    Object metric = outRec.getMetric(metricName);
    String type = (String) typeTable.get(metric.getClass());
    - emitMetric(namePrefix + metricName, type, metric.toString());
    + emitMetric(metricName, type, metric.toString());
    }
    -
    }

    private void emitMetric(String name, String type, String value)

    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor

    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • David Bowen (JIRA) at Mar 27, 2007 at 9:50 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484609 ]

    David Bowen commented on HADOOP-1163:
    -------------------------------------

    +1 code reviewed. Looks good.



    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor

    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Michael Bieniosek (JIRA) at Apr 2, 2007 at 9:32 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Michael Bieniosek updated HADOOP-1163:
    --------------------------------------

    Status: Patch Available (was: Open)
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor

    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Michael Bieniosek (JIRA) at Apr 2, 2007 at 9:34 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Michael Bieniosek updated HADOOP-1163:
    --------------------------------------

    Attachment: hostname-not-part-of-ganglia-record.patch

    Attach my patch the jira way
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor
    Attachments: hostname-not-part-of-ganglia-record.patch


    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hadoop QA (JIRA) at Apr 2, 2007 at 10:06 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486152 ]

    Hadoop QA commented on HADOOP-1163:
    -----------------------------------

    -1, because the patch command could not apply the latest attachment http://issues.apache.org as a patch to trunk revision http://svn.apache.org/repos/asf/lucene/hadoop/trunk/524929. Please note that this message is automatically generated and may represent a problem with the automation system and not the patch. Results are at http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor
    Attachments: hostname-not-part-of-ganglia-record.patch


    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hadoop QA (JIRA) at Apr 3, 2007 at 12:40 am
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486187 ]

    Hadoop QA commented on HADOOP-1163:
    -----------------------------------

    +1, because http://issues.apache.org/jira/secure/attachment/12354789/hostname-not-part-of-ganglia-record.patch applied and successfully tested against trunk revision http://svn.apache.org/repos/asf/lucene/hadoop/trunk/524929. Results are at http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor
    Attachments: hostname-not-part-of-ganglia-record.patch


    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Tom White (JIRA) at Apr 4, 2007 at 12:52 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Tom White updated HADOOP-1163:
    ------------------------------

    Status: Open (was: Patch Available)

    Michael,
    The patch no longer applies cleanly due to a conflict with HADOOP-1190 (which has been committed) - would you be able to regenerate it please? Thanks.
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor
    Attachments: hostname-not-part-of-ganglia-record.patch


    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Michael Bieniosek (JIRA) at Apr 4, 2007 at 4:46 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Michael Bieniosek updated HADOOP-1163:
    --------------------------------------

    Status: Patch Available (was: Open)
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor
    Attachments: hostname-not-part-of-ganglia-record-2.patch, hostname-not-part-of-ganglia-record.patch


    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Michael Bieniosek (JIRA) at Apr 4, 2007 at 4:46 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Michael Bieniosek updated HADOOP-1163:
    --------------------------------------

    Attachment: hostname-not-part-of-ganglia-record-2.patch

    attaching updated patch
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor
    Attachments: hostname-not-part-of-ganglia-record-2.patch, hostname-not-part-of-ganglia-record.patch


    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Tom White (JIRA) at Apr 4, 2007 at 7:01 pm
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Tom White updated HADOOP-1163:
    ------------------------------

    Resolution: Fixed
    Fix Version/s: 0.13.0
    Status: Resolved (was: Patch Available)

    I've just committed this. Thanks Michael!
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor
    Fix For: 0.13.0

    Attachments: hostname-not-part-of-ganglia-record-2.patch, hostname-not-part-of-ganglia-record.patch


    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Hadoop QA (JIRA) at Apr 5, 2007 at 11:22 am
    [ https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486926 ]

    Hadoop QA commented on HADOOP-1163:
    -----------------------------------

    Integrated in Hadoop-Nightly #48 (See http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/48/)
    Ganglia metrics reporting is misconfigured
    ------------------------------------------

    Key: HADOOP-1163
    URL: https://issues.apache.org/jira/browse/HADOOP-1163
    Project: Hadoop
    Issue Type: Bug
    Components: metrics
    Affects Versions: 0.12.1
    Environment: ganglia-3.0.3
    Reporter: Michael Bieniosek
    Priority: Minor
    Fix For: 0.13.0

    Attachments: hostname-not-part-of-ganglia-record-2.patch, hostname-not-part-of-ganglia-record.patch


    In hadoop-metrics.properties, I set mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext.
    If I then get the gmond xml feed from the gmond server, I get this:
    <METRIC NAME="load_one" VAL="1.04" TYPE="float" UNITS="" TN="28" TMAX="70" DMAX="0" SLOPE="both" SOURCE="gmond"/>
    ...
    <METRIC NAME="datanode.myhostname.bytes_read" VAL="657927" TYPE="int32" UNITS="" TN="5696" TMAX="60" DMAX="0" SLOPE="both" SOURCE="gmetric"/>
    Because the bytes_read metric has the datanode.hostname prefix, it will not aggregate with metrics from other hosts properly.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedMar 27, '07 at 7:47p
activeApr 5, '07 at 11:22a
posts12
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Hadoop QA (JIRA): 12 posts

People

Translate

site design / logo © 2022 Grokbase