You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2023/02/01 13:28:00 UTC

[jira] [Resolved] (HADOOP-18584) [NFS GW] Fix regression after netty4 migration

     [ https://issues.apache.org/jira/browse/HADOOP-18584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei-Chiu Chuang resolved HADOOP-18584.
--------------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

> [NFS GW] Fix regression after netty4 migration
> ----------------------------------------------
>
>                 Key: HADOOP-18584
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18584
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.4.0
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>
> Two bugs were found recently. Both related to hadoop portmap utility.
> (1) The ChannelHandler that can be added to a ChannelPipeline in Netty4 must be Shareable. However, IdleStateHandler, used by Portmap is not. We need to fix it otherwise hadoop portmap may fail to start.
> (2) RpcUdpResponseStage does not get the request from client (hadoop mountd) because of response type mismatch, and therefore it does not respond back to client request.
> This is a regression from HADOOP-11245 but I consider it not a blocker, because most recent Linux distro supports rpcbind and there's little reason to use Hadoop's portmap.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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