[
https://issues.apache.org/jira/browse/HADOOP-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643348#action_12643348
]
Raghu Angadi commented on HADOOP-4499:
--------------------------------------
Thanks Hairong.
Here is test-patch output :
{noformat}
[exec] -1 overall.
[exec] +1 @author. The patch does not contain any @author tags.
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
{noformat}
This functionality is already covered TestDataBlockScanner.
> DFSClient should invoke checksumOk only once.
> ---------------------------------------------
>
> Key: HADOOP-4499
> URL: https://issues.apache.org/jira/browse/HADOOP-4499
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.18.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Priority: Blocker
> Fix For: 0.19.1
>
> Attachments: HADOOP-4499-branch-19.patch, HADOOP-4499.patch
>
>
> This is a follow up for HADOOP-3914. HADOOP-3914 added a log when DFSClient
> tries to invoke checksumOk more than once. This jira is mainly for removing
> the debug log since we know why it happens.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
