hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandr (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6338) MR AppMaster does not honor ephemeral port range
Date Fri, 15 Jan 2016 17:47:40 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102172#comment-15102172

Alexandr commented on MAPREDUCE-6338:

Hello, [~bleuleon], you said : "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.".

So, do we have the solution for random web ports ? I'm trying to configure hadoop with 2 nodes
and with firewall enable. I can not do this because CantainerLauncher opens random port:

2015-12-16 16:00:14,775 INFO [ContainerLauncher #4]
org.apache.hadoop.ipc.Client: Retrying connect to server:
ub2simpl500/ Already tried 9 time(s); retry policy is
RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000

> 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
>              Labels: BB2015-05-TBR
>         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

View raw message