[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon reopened HDFS-877: ------------------------------ This bug fix should go in 0.21 as well, I think. The current patch doesn't apply, but I'll try to get to one tomorrow or early next week. I ran the new unit test against unpatched 21 and three out of the four cases failed (which is a regression from unpatched 0.20 where only 1/4 fail). > Client-driven block verification not functioning > ------------------------------------------------ > > Key: HDFS-877 > URL: https://issues.apache.org/jira/browse/HDFS-877 > Project: Hadoop HDFS > Issue Type: Bug > Components: hdfs client, test > Affects Versions: 0.20.1, 0.21.0, 0.22.0 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Fix For: 0.22.0 > > Attachments: hdfs-877-branch20.txt, hdfs-877.txt, hdfs-877.txt, > hdfs-877.txt, hdfs-877.txt, hdfs-877.txt, hdfs-877.txt > > > This is actually the reason for HDFS-734 (TestDatanodeBlockScanner timing > out). The issue is that DFSInputStream relies on readChunk being called one > last time at the end of the file in order to receive the > lastPacketInBlock=true packet from the DN. However, DFSInputStream.read > checks pos < getFileLength() before issuing the read. Thus gotEOS never > shifts to true and checksumOk() is never called. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.