hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4079) Allow MR AppMaster to limit ephemeral port range.
Date Wed, 18 Apr 2012 14:35:38 GMT

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

Robert Joseph Evans updated MAPREDUCE-4079:

    Target Version/s: 0.23.2, 2.0.0  (was: 2.0.0, 0.23.2)
              Status: Patch Available  (was: Open)
> Allow MR AppMaster to limit ephemeral port range.
> -------------------------------------------------
>                 Key: MAPREDUCE-4079
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4079
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.2, 2.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>         Attachments: MR-4079-full-branch-0.23.txt, MR-4079-full-branch-0.23.txt, MR-4079-full-branch-0.23.txt,
MR-4079-trunk.txt, MR-4079-trunk.txt, MR-4079-trunk.txt, MR-4079-trunk.txt
> Having the MapReduce Application Masters bind to any ephemeral port makes it very difficult
to setup ACLs.  mapreduce.job.am-access-disabled from MAPREDUCE-3251 is not a practical permanent
solution for all jobs.  Especially for tools like pig where they are not aware of mapreduce.job.am-access-disabled
and may deal with it properly.
> We should add in a config option that would allow someone to restrict the range of ports
that the MR-AM can bind to.  It will slow down startup in some cases because we will have
to probe for open ports instead of just asking the OS to find one for us.  But we can make
that conditional on this config so users who do not set this config do not see any performance

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message