[
https://issues.apache.org/jira/browse/HDFS-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930106#comment-13930106
]
Hadoop QA commented on HDFS-6086:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12633862/HDFS-6086.002.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6370//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6370//console
This message is automatically generated.
> Fix a case where zero-copy or no-checksum reads were not allowed even when
> the block was cached
> -----------------------------------------------------------------------------------------------
>
> Key: HDFS-6086
> URL: https://issues.apache.org/jira/browse/HDFS-6086
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode
> Affects Versions: 2.4.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-6086.001.patch, HDFS-6086.002.patch
>
>
> We need to fix a case where zero-copy or no-checksum reads are not allowed
> even when the block is cached. The case is when the block is cached before
> the {{REQUEST_SHORT_CIRCUIT_FDS}} operation begins. In this case,
> {{DataXceiver}} needs to consult the {{ShortCircuitRegistry}} to see if the
> block is cached, rather than relying on a callback.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
