[ 
https://issues.apache.org/jira/browse/HDFS-12566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201117#comment-16201117
 ] 

Hanisha Koneru commented on HDFS-12566:
---------------------------------------

Hi [~lukmajercak], did you see this exception anywhere other than in 
TestDataTransferProtocol#testDataTransferProtocol? 
As far as I checked, the {{requestedChecksum}} cannot be null in normal 
conditions. Is there any other object that can potentially be null in 
BlockReceiver?

> BlockReceiver can leak FileInputStream
> --------------------------------------
>
>                 Key: HDFS-12566
>                 URL: https://issues.apache.org/jira/browse/HDFS-12566
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, hdfs
>            Reporter: Lukas Majercak
>            Assignee: Lukas Majercak
>            Priority: Minor
>         Attachments: HDFS-12566.001.patch
>
>
> BlockReceiver's constructor can leak file handles if it encounters null 
> pointer exceptions. One example of this is 
> TestDataTransferProtocol.testDataTransferProtocol:
> java.lang.NullPointerException
>       at 
> org.apache.hadoop.hdfs.server.datanode.BlockReceiver.<init>(BlockReceiver.java:263)
>       at 
> org.apache.hadoop.hdfs.server.datanode.DataXceiver.getBlockReceiver(DataXceiver.java:1291)
>       at 
> org.apache.hadoop.hdfs.server.datanode.DataXceiver.writeBlock(DataXceiver.java:758)
>       at 
> org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.opWriteBlock(Receiver.java:173)
>       at 
> org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.processOp(Receiver.java:107)
>       at 
> org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:290)
>       at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to