[
https://issues.apache.org/jira/browse/MAPREDUCE-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumana Sathish updated MAPREDUCE-6338:
--------------------------------------
Description:
# 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
was:
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
> 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
> Priority: Major
> Fix For: 2.9.0, 3.0.0-alpha4
>
> Attachments: MAPREDUCE-6338.002.patch, MAPREDUCE-6338.003.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
