You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/11/22 02:54:58 UTC

[jira] [Commented] (HDFS-7578) NFS WRITE and COMMIT responses should always use the channel pipeline

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

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

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red} HDFS-7578 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-7578 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12730282/HDFS-7578.003.patch |
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/17624/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


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
>              Labels: BB2015-05-TBR
>         Attachments: HDFS-7578.001.patch, HDFS-7578.002.patch, HDFS-7578.003.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)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org