You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Cheng (JIRA)" <ji...@apache.org> on 2009/06/23 20:56:07 UTC
[jira] Created: (CHUKWA-328) NPE for empty chukwarecord sequence
file
NPE for empty chukwarecord sequence file
----------------------------------------
Key: CHUKWA-328
URL: https://issues.apache.org/jira/browse/CHUKWA-328
Project: Hadoop Chukwa
Issue Type: Bug
Reporter: Cheng
Assignee: Cheng
2009-06-23 17:21:44,307 ERROR main MetricDataLoaderPool - java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at org.apache.hadoop.chukwa.dataloader.MetricDataLoaderPool.load(MetricDataLoaderPool.java:49)
at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.processDemuxPigOutput(PostProcessorManager.java:188)
at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.start(PostProcessorManager.java:145)
at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.main(PostProcessorManager.java:80)
Caused by: java.lang.NullPointerException
at org.apache.hadoop.chukwa.extraction.engine.ChukwaRecord.getValue(ChukwaRecord.java:46)
at org.apache.hadoop.chukwa.extraction.engine.RecordUtil.getClusterName(RecordUtil.java:14)
at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.run(MetricDataLoader.java:518)
at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.call(MetricDataLoader.java:567)
at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.call(MetricDataLoader.java:50)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
The root cause is that we should not use the ChukwaRecord if there is no record in the file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-328) NPE for empty chukwarecord sequence
file
Posted by "Cheng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheng updated CHUKWA-328:
-------------------------
Attachment: chukwa-328.patch
patch provided.
> NPE for empty chukwarecord sequence file
> ----------------------------------------
>
> Key: CHUKWA-328
> URL: https://issues.apache.org/jira/browse/CHUKWA-328
> Project: Hadoop Chukwa
> Issue Type: Bug
> Reporter: Cheng
> Assignee: Cheng
> Attachments: chukwa-328.patch
>
>
> 2009-06-23 17:21:44,307 ERROR main MetricDataLoaderPool - java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
> at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoaderPool.load(MetricDataLoaderPool.java:49)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.processDemuxPigOutput(PostProcessorManager.java:188)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.start(PostProcessorManager.java:145)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.main(PostProcessorManager.java:80)
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.chukwa.extraction.engine.ChukwaRecord.getValue(ChukwaRecord.java:46)
> at org.apache.hadoop.chukwa.extraction.engine.RecordUtil.getClusterName(RecordUtil.java:14)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.run(MetricDataLoader.java:518)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.call(MetricDataLoader.java:567)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.call(MetricDataLoader.java:50)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
> The root cause is that we should not use the ChukwaRecord if there is no record in the file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-328) NPE for empty chukwarecord sequence
file
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Yang updated CHUKWA-328:
-----------------------------
Fix Version/s: 0.3.0
0.2.0
Affects Version/s: 0.2.0
Status: Patch Available (was: Open)
+1 Looks good.
> NPE for empty chukwarecord sequence file
> ----------------------------------------
>
> Key: CHUKWA-328
> URL: https://issues.apache.org/jira/browse/CHUKWA-328
> Project: Hadoop Chukwa
> Issue Type: Bug
> Affects Versions: 0.2.0
> Reporter: Cheng
> Assignee: Cheng
> Fix For: 0.2.0, 0.3.0
>
> Attachments: chukwa-328.patch
>
>
> 2009-06-23 17:21:44,307 ERROR main MetricDataLoaderPool - java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
> at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoaderPool.load(MetricDataLoaderPool.java:49)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.processDemuxPigOutput(PostProcessorManager.java:188)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.start(PostProcessorManager.java:145)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.main(PostProcessorManager.java:80)
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.chukwa.extraction.engine.ChukwaRecord.getValue(ChukwaRecord.java:46)
> at org.apache.hadoop.chukwa.extraction.engine.RecordUtil.getClusterName(RecordUtil.java:14)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.run(MetricDataLoader.java:518)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.call(MetricDataLoader.java:567)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.call(MetricDataLoader.java:50)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
> The root cause is that we should not use the ChukwaRecord if there is no record in the file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CHUKWA-328) NPE for empty chukwarecord sequence
file
Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Yang updated CHUKWA-328:
-----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this, thanks Cheng.
> NPE for empty chukwarecord sequence file
> ----------------------------------------
>
> Key: CHUKWA-328
> URL: https://issues.apache.org/jira/browse/CHUKWA-328
> Project: Hadoop Chukwa
> Issue Type: Bug
> Affects Versions: 0.2.0
> Reporter: Cheng
> Assignee: Cheng
> Fix For: 0.2.0, 0.3.0
>
> Attachments: chukwa-328.patch
>
>
> 2009-06-23 17:21:44,307 ERROR main MetricDataLoaderPool - java.util.concurrent.ExecutionException: java.lang.NullPointerException
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
> at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoaderPool.load(MetricDataLoaderPool.java:49)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.processDemuxPigOutput(PostProcessorManager.java:188)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.start(PostProcessorManager.java:145)
> at org.apache.hadoop.chukwa.extraction.demux.PostProcessorManager.main(PostProcessorManager.java:80)
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.chukwa.extraction.engine.ChukwaRecord.getValue(ChukwaRecord.java:46)
> at org.apache.hadoop.chukwa.extraction.engine.RecordUtil.getClusterName(RecordUtil.java:14)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.run(MetricDataLoader.java:518)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.call(MetricDataLoader.java:567)
> at org.apache.hadoop.chukwa.dataloader.MetricDataLoader.call(MetricDataLoader.java:50)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
> The root cause is that we should not use the ChukwaRecord if there is no record in the file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.