[
https://issues.apache.org/jira/browse/HDFS-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137651#comment-13137651
]
Hadoop QA commented on HDFS-2500:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501160/hdfs-2500-1.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hdfs.TestFileAppend2
org.apache.hadoop.hdfs.TestBalancerBandwidth
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/1475//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1475//console
This message is automatically generated.
> Avoid file system operations in BPOfferService thread while processing deletes
> ------------------------------------------------------------------------------
>
> Key: HDFS-2500
> URL: https://issues.apache.org/jira/browse/HDFS-2500
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-2500-1.patch, hdfs-2500.txt
>
>
> While running a workload with concurrent writes and deletes, I saw a lot of
> NotReplicatedYetExceptions being thrown due to late arrivals of blockReceived
> reports from the DN. Looking at the DN logs, I found that the blockReceived
> message was being delayed as much as 15 seconds because the OfferService
> thread was blocked on file system operations processing deletes. We
> previously moved the deletions to another thread, but it still accesses the
> file system to determine the block length in the main thread. On a heavily
> loaded system this can take a long time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
