You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Michael Bieniosek (JIRA)" <ji...@apache.org> on 2008/09/09 23:37:44 UTC
[jira] Created: (HADOOP-4137) NPE in GangliaContext.xdr_string
(GangliaContext.java:195)
NPE in GangliaContext.xdr_string (GangliaContext.java:195)
----------------------------------------------------------
Key: HADOOP-4137
URL: https://issues.apache.org/jira/browse/HADOOP-4137
Project: Hadoop Core
Issue Type: Bug
Components: metrics
Affects Versions: 0.18.0
Reporter: Michael Bieniosek
Exception in thread "Timer thread for monitoring dfs" java.lang.NullPointerException
at org.apache.hadoop.metrics.ganglia.GangliaContext.xdr_string(GangliaContext.java:195)
at org.apache.hadoop.metrics.ganglia.GangliaContext.emitMetric(GangliaContext.java:138)
at org.apache.hadoop.metrics.ganglia.GangliaContext.emitRecord(GangliaContext.java:123)
at org.apache.hadoop.metrics.spi.AbstractMetricsContext.emitRecords(AbstractMetricsContext.java:304)
at org.apache.hadoop.metrics.spi.AbstractMetricsContext.timerEvent(AbstractMetricsContext.java:290)
at org.apache.hadoop.metrics.spi.AbstractMetricsContext.access$000(AbstractMetricsContext.java:50)
at org.apache.hadoop.metrics.spi.AbstractMetricsContext$1.run(AbstractMetricsContext.java:249)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
It looks like this caused the datanode to hang, though I accidentally killed the datanode before I could dump its stack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4137) NPE in GangliaContext.xdr_string
(GangliaContext.java:195)
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated HADOOP-4137:
----------------------------------
Status: Open (was: Patch Available)
> NPE in GangliaContext.xdr_string (GangliaContext.java:195)
> ----------------------------------------------------------
>
> Key: HADOOP-4137
> URL: https://issues.apache.org/jira/browse/HADOOP-4137
> Project: Hadoop Core
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.18.1, 0.18.0
> Reporter: Michael Bieniosek
> Attachments: hadoop_ganglia_npe-4137.patch, hadoop_ganglia_npe-4137.patch
>
>
> Exception in thread "Timer thread for monitoring dfs" java.lang.NullPointerException
> at org.apache.hadoop.metrics.ganglia.GangliaContext.xdr_string(GangliaContext.java:195)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitMetric(GangliaContext.java:138)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitRecord(GangliaContext.java:123)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.emitRecords(AbstractMetricsContext.java:304)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.timerEvent(AbstractMetricsContext.java:290)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.access$000(AbstractMetricsContext.java:50)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext$1.run(AbstractMetricsContext.java:249)
> at java.util.TimerThread.mainLoop(Unknown Source)
> at java.util.TimerThread.run(Unknown Source)
> It looks like this caused the datanode to hang, though I accidentally killed the datanode before I could dump its stack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-4137) NPE in GangliaContext.xdr_string
(GangliaContext.java:195)
Posted by "Brian Bockelman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Bockelman resolved HADOOP-4137.
-------------------------------------
Resolution: Duplicate
> NPE in GangliaContext.xdr_string (GangliaContext.java:195)
> ----------------------------------------------------------
>
> Key: HADOOP-4137
> URL: https://issues.apache.org/jira/browse/HADOOP-4137
> Project: Hadoop Core
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.18.0, 0.18.1
> Reporter: Michael Bieniosek
> Attachments: hadoop_ganglia_npe-4137.patch, hadoop_ganglia_npe-4137.patch
>
>
> Exception in thread "Timer thread for monitoring dfs" java.lang.NullPointerException
> at org.apache.hadoop.metrics.ganglia.GangliaContext.xdr_string(GangliaContext.java:195)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitMetric(GangliaContext.java:138)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitRecord(GangliaContext.java:123)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.emitRecords(AbstractMetricsContext.java:304)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.timerEvent(AbstractMetricsContext.java:290)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.access$000(AbstractMetricsContext.java:50)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext$1.run(AbstractMetricsContext.java:249)
> at java.util.TimerThread.mainLoop(Unknown Source)
> at java.util.TimerThread.run(Unknown Source)
> It looks like this caused the datanode to hang, though I accidentally killed the datanode before I could dump its stack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4137) NPE in GangliaContext.xdr_string
(GangliaContext.java:195)
Posted by "Brian Bockelman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Bockelman updated HADOOP-4137:
------------------------------------
Affects Version/s: 0.18.1
Status: Patch Available (was: Open)
Catch the NPE reported on bug HADOOP-4137; also fixes another NPE which was immediately triggered in 0.18.1 after applying the patch.
With this patch and the patch for HADOOP-3422, Ganglia metrics are working again.
> NPE in GangliaContext.xdr_string (GangliaContext.java:195)
> ----------------------------------------------------------
>
> Key: HADOOP-4137
> URL: https://issues.apache.org/jira/browse/HADOOP-4137
> Project: Hadoop Core
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.18.1, 0.18.0
> Reporter: Michael Bieniosek
> Attachments: hadoop_ganglia_npe-4137.patch
>
>
> Exception in thread "Timer thread for monitoring dfs" java.lang.NullPointerException
> at org.apache.hadoop.metrics.ganglia.GangliaContext.xdr_string(GangliaContext.java:195)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitMetric(GangliaContext.java:138)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitRecord(GangliaContext.java:123)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.emitRecords(AbstractMetricsContext.java:304)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.timerEvent(AbstractMetricsContext.java:290)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.access$000(AbstractMetricsContext.java:50)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext$1.run(AbstractMetricsContext.java:249)
> at java.util.TimerThread.mainLoop(Unknown Source)
> at java.util.TimerThread.run(Unknown Source)
> It looks like this caused the datanode to hang, though I accidentally killed the datanode before I could dump its stack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4137) NPE in GangliaContext.xdr_string
(GangliaContext.java:195)
Posted by "Brian Bockelman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Bockelman updated HADOOP-4137:
------------------------------------
Attachment: hadoop_ganglia_npe-4137.patch
> NPE in GangliaContext.xdr_string (GangliaContext.java:195)
> ----------------------------------------------------------
>
> Key: HADOOP-4137
> URL: https://issues.apache.org/jira/browse/HADOOP-4137
> Project: Hadoop Core
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.18.0, 0.18.1
> Reporter: Michael Bieniosek
> Attachments: hadoop_ganglia_npe-4137.patch
>
>
> Exception in thread "Timer thread for monitoring dfs" java.lang.NullPointerException
> at org.apache.hadoop.metrics.ganglia.GangliaContext.xdr_string(GangliaContext.java:195)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitMetric(GangliaContext.java:138)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitRecord(GangliaContext.java:123)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.emitRecords(AbstractMetricsContext.java:304)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.timerEvent(AbstractMetricsContext.java:290)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.access$000(AbstractMetricsContext.java:50)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext$1.run(AbstractMetricsContext.java:249)
> at java.util.TimerThread.mainLoop(Unknown Source)
> at java.util.TimerThread.run(Unknown Source)
> It looks like this caused the datanode to hang, though I accidentally killed the datanode before I could dump its stack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-4137) NPE in GangliaContext.xdr_string
(GangliaContext.java:195)
Posted by "Brian Bockelman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Bockelman updated HADOOP-4137:
------------------------------------
Attachment: hadoop_ganglia_npe-4137.patch
Updated patch: Silly me, Ganglia has no long data type - and I mapped it to int32, which overflows quickly (especially when reporting bytes transferred!).
This now maps Long to float in Ganglia.
> NPE in GangliaContext.xdr_string (GangliaContext.java:195)
> ----------------------------------------------------------
>
> Key: HADOOP-4137
> URL: https://issues.apache.org/jira/browse/HADOOP-4137
> Project: Hadoop Core
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.18.0, 0.18.1
> Reporter: Michael Bieniosek
> Attachments: hadoop_ganglia_npe-4137.patch, hadoop_ganglia_npe-4137.patch
>
>
> Exception in thread "Timer thread for monitoring dfs" java.lang.NullPointerException
> at org.apache.hadoop.metrics.ganglia.GangliaContext.xdr_string(GangliaContext.java:195)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitMetric(GangliaContext.java:138)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitRecord(GangliaContext.java:123)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.emitRecords(AbstractMetricsContext.java:304)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.timerEvent(AbstractMetricsContext.java:290)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.access$000(AbstractMetricsContext.java:50)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext$1.run(AbstractMetricsContext.java:249)
> at java.util.TimerThread.mainLoop(Unknown Source)
> at java.util.TimerThread.run(Unknown Source)
> It looks like this caused the datanode to hang, though I accidentally killed the datanode before I could dump its stack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4137) NPE in GangliaContext.xdr_string
(GangliaContext.java:195)
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636855#action_12636855 ]
Hadoop QA commented on HADOOP-4137:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12391474/hadoop_ganglia_npe-4137.patch
against trunk revision 701476.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3432/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3432/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3432/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3432/console
This message is automatically generated.
> NPE in GangliaContext.xdr_string (GangliaContext.java:195)
> ----------------------------------------------------------
>
> Key: HADOOP-4137
> URL: https://issues.apache.org/jira/browse/HADOOP-4137
> Project: Hadoop Core
> Issue Type: Bug
> Components: metrics
> Affects Versions: 0.18.0, 0.18.1
> Reporter: Michael Bieniosek
> Attachments: hadoop_ganglia_npe-4137.patch
>
>
> Exception in thread "Timer thread for monitoring dfs" java.lang.NullPointerException
> at org.apache.hadoop.metrics.ganglia.GangliaContext.xdr_string(GangliaContext.java:195)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitMetric(GangliaContext.java:138)
> at org.apache.hadoop.metrics.ganglia.GangliaContext.emitRecord(GangliaContext.java:123)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.emitRecords(AbstractMetricsContext.java:304)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.timerEvent(AbstractMetricsContext.java:290)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext.access$000(AbstractMetricsContext.java:50)
> at org.apache.hadoop.metrics.spi.AbstractMetricsContext$1.run(AbstractMetricsContext.java:249)
> at java.util.TimerThread.mainLoop(Unknown Source)
> at java.util.TimerThread.run(Unknown Source)
> It looks like this caused the datanode to hang, though I accidentally killed the datanode before I could dump its stack.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.