[
https://issues.apache.org/jira/browse/MAPREDUCE-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522697#comment-14522697
]
Frank Nguyen commented on MAPREDUCE-6338:
-----------------------------------------
This patch is working for me. Just got to figure out the checkstyle issue to
get this patch accepted.
Rohith, you are correct, the web port that opens up temporarily while the job
is in progress is also random. I think a separate JIRA can be created for it
since it does not stop the Job from completing successfully. The problem might
be in MRClientService.java at the following line:
webApp =
WebApps.$for("mapreduce", AppContext.class, appContext, "ws")
.withHttpPolicy(conf, Policy.HTTP_ONLY).start(new AMWebApp());
> MR AppMaster does not honor ephemeral port range
> ------------------------------------------------
>
> Key: MAPREDUCE-6338
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6338
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am, mrv2
> Affects Versions: 2.6.0
> Reporter: Frank Nguyen
> Assignee: Frank Nguyen
> Attachments: MAPREDUCE-6338.002.patch
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
