[ https://issues.apache.org/jira/browse/HDFS-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803837#action_12803837 ]
Todd Lipcon commented on HDFS-877: ---------------------------------- I think it's a regression in that there now exists a unit test which fails 1 case in 0.20 and 3 cases in 0.21. The fact that TestDataBlockScanner passes doesn't necessarily mean there's no bug, just that the bug isn't exposed by a test. I don't think it's absolutely critical, but it seems worth fixing. If you disagree, I'm happy to have this issue closed again. > 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.