[
https://issues.apache.org/jira/browse/HDFS-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177669#comment-14177669
]
Hadoop QA commented on HDFS-7259:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12675970/HDFS-7259.002.patch
against trunk revision e90718f.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 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 2.0.3) 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-common-project/hadoop-nfs hadoop-hdfs-project/hadoop-hdfs-nfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/8463//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8463//console
This message is automatically generated.
> Unresponseive NFS mount point due to deferred COMMIT response
> -------------------------------------------------------------
>
> Key: HDFS-7259
> URL: https://issues.apache.org/jira/browse/HDFS-7259
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: nfs
> Affects Versions: 2.2.0
> Reporter: Brandon Li
> Assignee: Brandon Li
> Attachments: HDFS-7259.001.patch, HDFS-7259.002.patch
>
>
> Since the gateway can't commit random write, it caches the COMMIT requests in
> a queue and send back response only when the data can be committed or stream
> timeout (failure in the latter case). This could cause problems two patterns:
> (1) file uploading failure
> (2) the mount dir is stuck on the same client, but other NFS clients can
> still access NFS gateway.
> The error pattern (2) is because there are too many COMMIT requests pending,
> so the NFS client can't send any other requests(e.g., for "ls") to NFS
> gateway with its pending requests limit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
