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 "Trevor Robinson (JIRA)" <ji...@apache.org> on 2012/10/30 21:16:13 UTC
[jira] [Resolved] (HDFS-3822) TestWebHDFS fails intermittently with
NullPointerException
[ https://issues.apache.org/jira/browse/HDFS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trevor Robinson resolved HDFS-3822.
-----------------------------------
Resolution: Duplicate
Release Note: Yes, this probably is a duplicate of HDFS-3664. The stack traces look the same, and I haven't seen it occur since that issue was fixed.
> TestWebHDFS fails intermittently with NullPointerException
> ----------------------------------------------------------
>
> Key: HDFS-3822
> URL: https://issues.apache.org/jira/browse/HDFS-3822
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.0.2-alpha
> Environment: Apache Maven 3.0.4
> Maven home: /usr/share/maven
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> Default locale: en_US, platform encoding: ISO-8859-1
> OS name: "linux", version: "3.2.0-25-generic", arch: "amd64", family: "unix"
> Reporter: Trevor Robinson
> Labels: test-fail
> Attachments: org.apache.hadoop.hdfs.web.TestWebHDFS-output.txt, org.apache.hadoop.hdfs.web.TestWebHDFS.txt
>
>
> I've hit this test failure a few times in trunk:
> {noformat}
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 58.835 sec <<< FAILURE!
> testNamenodeRestart(org.apache.hadoop.hdfs.web.TestWebHDFS) Time elapsed: 52.105 sec <<< FAILURE!
> java.lang.AssertionError: There are 1 exception(s):
> Exception 0: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.RemoteException): java.lang.NullPointerExcept
> ion
> at org.apache.hadoop.hdfs.server.blockmanagement.BlocksMap.getBlockCollection(BlocksMap.java:101)
> at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.getBlockCollection(BlockManager.java:2926)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.isValidBlock(FSNamesystem.java:4474)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.allocateBlock(FSNamesystem.java:2439)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2200)
> at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:471)
> at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtoco
> lServerSideTranslatorPB.java:295)
> at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMetho
> d(ClientNamenodeProtocolProtos.java:43388)
> at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:473)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:898)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1693)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1689)
> {noformat}
> It appears that {{close}} has been called on the {{BlocksMap}} before {{getBlockCollection}}.
--
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