[ 
https://issues.apache.org/jira/browse/HDFS-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520637#comment-14520637
 ] 

Hadoop QA commented on HDFS-7578:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply 
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12689584/HDFS-7578.002.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / aa22450 |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/10464/console |


This message was automatically generated.

> NFS WRITE and COMMIT responses should always use the channel pipeline
> ---------------------------------------------------------------------
>
>                 Key: HDFS-7578
>                 URL: https://issues.apache.org/jira/browse/HDFS-7578
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: nfs
>    Affects Versions: 2.7.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>         Attachments: HDFS-7578.001.patch, HDFS-7578.002.patch
>
>
> Write and Commit responses directly write data to the channel instead of 
> propagating it to the next immediate handler in the channel pipeline. 
> Not following Netty channel pipeline model could be problematic. We don't 
> know whether it could cause any resource leak or performance issue especially 
> the internal pipeline implementation keeps changing with newer Netty releases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to