hadoop-mapreduce-issues mailing list archives

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

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

Allen Wittenauer commented on MAPREDUCE-2750:

So basically the argument for ephemeral ports is that it is too hard to provide different
config files to run the 2+ services on the same box for testing? 

I would think for testing predictability would be a great quality to have...

But yes, out of the box this needs to have fix port for production purposes. (... and not
8080! That's just stunningly bad.)  For testing, it makes sense to provide a different config
that turns on ephemeral-ness if that is really desired.  (Which doesn't make sense to me at
all, but whatever.)

> [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

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


View raw message