[
https://issues.apache.org/jira/browse/HDFS-7578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265320#comment-14265320
]
Brandon Li commented on HDFS-7578:
----------------------------------
[~wheat9], I am not sure if I got the whole idea. We could use
ChannelHandlerConctext to get Channel and then get remoteAddress. Are you
suggesting not passing down remoteAddress or ChannelHandlerContext?
> 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)
