[HDFS-3822] TestWebHDFS fails intermittently with NullPointerException

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.2-alpha
• Component/s: test
• Labels: test-fail

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"

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.

• Assignee: Unassigned
• Reporter: Trevor Robinson
• Created: 20/Aug/12 23:13
• Updated: 30/Oct/12 20:15
• Resolved: 30/Oct/12 20:15

Description

I've hit this test failure a few times in trunk:

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)

It appears that close has been called on the BlocksMap before getBlockCollection.

Issue Links

• relates to: HDFS-3664 BlockManager race when stopping active services