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

Hadoop QA commented on MAPREDUCE-6338:
--------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 33s | Pre-patch trunk compilation is 
healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any 
@author tags. |
| {color:red}-1{color} | tests included |   0m  0s | The patch doesn't appear 
to include any new or modified tests.  Please justify why no new tests are 
needed for this patch. Also please list what manual steps were performed to 
verify this patch. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that 
end in whitespace. |
| {color:red}-1{color} | javac |   4m 20s | The patch appears to cause the 
build to fail. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12728197/MAPREDUCE-6338.001.patch
 |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / a00e001 |
| Console output | 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5451/console |


This message was automatically generated.

> 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.001.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)

Reply via email to