hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2750) [MR-279] NodeManager should start its servers on ephemeral ports
Date Wed, 03 Aug 2011 14:18:27 GMT

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

Vinod Kumar Vavilapalli commented on MAPREDUCE-2750:
----------------------------------------------------

bq. Is there a reason someone would want to run multiple NodeManagers on a single host in
a production environment?
Two cases where I need this: (1) for benchmarks where I want to run many nodemanagers on a
single node and (2) tests so that multiple NMs can be started in MiniYARNClusters.

bq. Hadoop has way too many ephemeral ports as it is....
Any down-sides to this? I know Steve mentioned firewall issues, anything else too?

bq. How about making it an option to start on an ephemeral port, as in production it will
only complicate firewall setup
Thanks for that idea, that could work if we deem ephemeral ports as too limiting.

> [MR-279] NodeManager should start its servers on ephemeral ports 
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-2750
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2750
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>             Fix For: 0.23.0
>
>
> There is absolutely no need for NM to start ContainerManager on a standard port, it should
bind to an ephemeral port. Binding on ephemeral ports will help us start multiple NMs on a
single node without any issues.
> The same holds for the ResourceLocalizationService's server port and NM Http server's
port. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message