Tsz Wo (Nicholas), SZE created HDFS-4813:
--------------------------------------------

             Summary: BlocksMap may throw NullPointerException during shutdown
                 Key: HDFS-4813
                 URL: https://issues.apache.org/jira/browse/HDFS-4813
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode
            Reporter: Tsz Wo (Nicholas), SZE
            Priority: Minor


TestBlocksWithNotEnoughRacks may fail occasionally due to the bug:
{noformat}
java.lang.AssertionError: Test resulted in an unexpected exit
        at 
org.apache.hadoop.hdfs.MiniDFSCluster.shutdown(MiniDFSCluster.java:1416)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.TestBlocksWithNotEnoughRacks.__CLR3_0_226e5kj1ntz(TestBlocksWithNotEnoughRacks.java:373)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.TestBlocksWithNotEnoughRacks.testReduceReplFactorDueToRejoinRespectsRackPolicy(TestBlocksWithNotEnoughRacks.java:330)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        ...
{noformat}
At the end of the log:
{noformat}
2013-05-10 13:05:53,828 FATAL hdfs.MiniDFSCluster 
(MiniDFSCluster.java:shutdown(1413)) - Test resulted in an unexpected exit
org.apache.hadoop.util.ExitUtil$ExitException: java.lang.NullPointerException
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlocksMap.getBlockCollection(BlocksMap.java:77)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeReplicationWorkForBlocks(BlockManager.java:1153)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeReplicationWork(BlockManager.java:1128)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.computeDatanodeWork(BlockManager.java:3127)
        at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager$ReplicationMonitor.run(BlockManager.java:3089)
        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

Reply via email to