You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2012/09/13 03:54:07 UTC
[jira] [Created] (HDFS-3933) Unclean exit in ReplicationMonitor#run
occasionally causes tests to fail
Eli Collins created HDFS-3933:
---------------------------------
Summary: Unclean exit in ReplicationMonitor#run occasionally causes tests to fail
Key: HDFS-3933
URL: https://issues.apache.org/jira/browse/HDFS-3933
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.0.0-alpha
Reporter: Eli Collins
I've seen the following in jenkins jobs for TestHadoopArchives and TestBlockTokenWithDFS. We're not getting the initial ExitException thrown by ReplicationMonitor, just the log of the ExitException in MiniDFSCluster shutdown. Looks like the ExitException has no message so the throwable that resulted in the ExitException has no message, in which case it would be useful to capture the whole stacktrace of the throwable.
{noformat}
2012-09-12 18:22:08,370 FATAL [main] hdfs.MiniDFSCluster (MiniDFSCluster.java:shutdown(1355)) - Test resulted in an unexpected exit
org.apache.hadoop.util.ExitUtil$ExitException
at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:86)
at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:104)
at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager$ReplicationMonitor.run(BlockManager.java:3031)
at java.lang.Thread.run(Thread.java:662)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HDFS-3933) Unclean exit in
ReplicationMonitor#run occasionally causes tests to fail
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins resolved HDFS-3933.
-------------------------------
Resolution: Duplicate
Now that we can see the root cause, this is a dupe of HDFS-3936.
{noformat}
2012-09-13 18:22:07,575 FATAL [main] hdfs.MiniDFSCluster (MiniDFSCluster.java:shutdown(1355)) - Test resulted in an unexpected exit
org.apache.hadoop.util.ExitUtil$ExitException: Fatal exception with message null
stack trace
java.lang.NullPointerException
at org.apache.hadoop.hdfs.server.blockmanagement.BlocksMap.getBlockCollection(BlocksMap.java:101)
at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeReplicationWorkForBlocks(BlockManager.java:1132)
at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeReplicationWork(BlockManager.java:1107)
at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeDatanodeWork(BlockManager.java:3061)
at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager$ReplicationMonitor.run(BlockManager.java:3023)
at java.lang.Thread.run(Thread.java:662)
{noformat}
> Unclean exit in ReplicationMonitor#run occasionally causes tests to fail
> -------------------------------------------------------------------------
>
> Key: HDFS-3933
> URL: https://issues.apache.org/jira/browse/HDFS-3933
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Eli Collins
>
> I've seen the following in jenkins jobs for TestHadoopArchives and TestBlockTokenWithDFS. We're not getting the initial ExitException thrown by ReplicationMonitor, just the log of the ExitException in MiniDFSCluster shutdown. Looks like the ExitException has no message so the throwable that resulted in the ExitException has no message, in which case it would be useful to capture the whole stacktrace of the throwable.
> {noformat}
> 2012-09-12 18:22:08,370 FATAL [main] hdfs.MiniDFSCluster (MiniDFSCluster.java:shutdown(1355)) - Test resulted in an unexpected exit
> org.apache.hadoop.util.ExitUtil$ExitException
> at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:86)
> at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:104)
> at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager$ReplicationMonitor.run(BlockManager.java:3031)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira