[jira] [Updated] (MAPREDUCE-4079) Allow MR AppMaster to limit ephemeral port range.

["Robert Joseph Evans (Updated) (JIRA)" <ji...@apache.org>]

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

Robert Joseph Evans updated MAPREDUCE-4079:
-------------------------------------------

    Attachment: MR-4079-trunk.txt
                MR-4079-full-branch-0.23.txt

The trunk patch depends on the patch in HADOOP-8227.  I will put this JIRA in patch available once it is integrated in. 

Unfortunetly for 0.23 the RPC engine code is split among the projects so the patches for MAPREDUCE-4079 and HADOOP-8227 need to go in at the same time.  I have attached the full patch for branch-0.23 for both of these JIRAs.  Once both JIRAs are approved for trunk and branch-2.0, I can put the full patch into branch-0.23. 
                
> 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-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 degradation. 

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