[
https://issues.apache.org/jira/browse/HDFS-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804608#comment-13804608
]
Haohui Mai commented on HDFS-5288:
----------------------------------
Different servers have different requirements for timeouts, resource
managements, etcFor example, the portmap server only needs a small amount of
timeouts and very few numbers of threads, but the nfs gateway might not want
timeout at all and have a large numbers of threads, and associate each requests
with their memory consumptions. Moreover, it is important to let the client to
have full control of the pipelines, in which case logging, authentication,
interceptions, etc. can happen.
I agree that putting it in simple*server might simply the code to some extent.
I argue, however, they are bad abstractions since they are unable to capture
the vastly different requirements of each servers. The trade-offs here is to
expose the netty apis into the applications. I believe that it is worthwhile
doing so because the bootstrapping apis of netty are quite simple to use.
> Close idle connections in portmap
> ---------------------------------
>
> Key: HDFS-5288
> URL: https://issues.apache.org/jira/browse/HDFS-5288
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: nfs
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Attachments: HDFS-5288.000.patch
>
>
> Currently the portmap daemon does not close idle connections. The daemon
> should close any idle connections to save resources.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
