[MAPREDUCE-6338] MR AppMaster does not honor ephemeral port range

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.9.0, 3.0.0-alpha4
• Component/s: mr-am, mrv2
• Hadoop Flags: Reviewed
• Assignee: Frank Nguyen
• Reporter: Frank Nguyen
• Created: 24/Apr/15 05:02
• Updated: 07/Jun/18 21:42
• Resolved: 06/Feb/17 03:36

Description

1. The MR AppMaster should only use port ranges defined in the yarn.app.mapreduce.am.job.client.port-range property. On initial startup of the MRAppMaster, it does use the port range defined in the property. However, it also opens up a listener on a random ephemeral port. This is not the Jetty listener. It is another listener opened by the MRAppMaster via another thread and is recognized by the RM. Other nodes will try to communicate to it via that random port. With firewall settings on, the MR job will fail because the random port is not opened. This problem has caused others to have all OS ephemeral ports opened to have MR jobs run.

This is related to MAPREDUCE-4079

Issue Links

• is related to: HADOOP-12097 Allow port range to be specified while starting webapp
• is related to: MAPREDUCE-6404 Allow AM to specify a port range for starting its webapp