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

Hadoop QA commented on MAPREDUCE-4079:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12523199/MR-4079-trunk.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  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.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    -1 javac.  The patch appears to cause tar ant target to fail.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    -1 findbugs.  The patch appears to cause Findbugs (version 1.3.9) to fail.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    -1 core tests.  The patch failed these unit tests:
                  org.apache.hadoop.mapred.TestMiniMRClientCluster
                  org.apache.hadoop.mapreduce.v2.TestMROldApiJobs
                  org.apache.hadoop.mapred.TestJobCounters
                  org.apache.hadoop.mapreduce.lib.output.TestJobOutputCommitter
                  org.apache.hadoop.mapred.TestClusterMapReduceTestCase
                  org.apache.hadoop.mapred.TestJobName
                  org.apache.hadoop.mapreduce.v2.TestMiniMRProxyUser
                  org.apache.hadoop.mapreduce.v2.TestUberAM
                  org.apache.hadoop.mapred.TestClusterMRNotification
                  org.apache.hadoop.mapred.TestReduceFetch
                  org.apache.hadoop.mapreduce.TestChild
                  org.apache.hadoop.mapred.TestLazyOutput
                  org.apache.hadoop.mapred.TestReduceFetchFromPartialMem
                  org.apache.hadoop.mapreduce.v2.TestMRJobs
                  org.apache.hadoop.mapred.TestMiniMRWithDFSWithDistinctUsers
                  org.apache.hadoop.mapred.TestJobSysDirWithDFS
                  org.apache.hadoop.mapreduce.TestMapReduceLazyOutput
                  org.apache.hadoop.mapred.TestJobCleanup
                  org.apache.hadoop.mapreduce.v2.TestSpeculativeExecution
                  org.apache.hadoop.mapred.TestMiniMRChildTask

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2248//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2248//console

This message is automatically generated.
                
> Allow MR AppMaster to limit ephemeral port range.
> -------------------------------------------------
>
>                 Key: MAPREDUCE-4079
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4079
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mr-am, mrv2
>    Affects Versions: 0.23.2, 2.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>         Attachments: MR-4079-full-branch-0.23.txt, 
> MR-4079-full-branch-0.23.txt, MR-4079-full-branch-0.23.txt, 
> MR-4079-trunk.txt, MR-4079-trunk.txt, MR-4079-trunk.txt, MR-4079-trunk.txt
>
>
> Having the MapReduce Application Masters bind to any ephemeral port makes it 
> very difficult to setup ACLs.  mapreduce.job.am-access-disabled from 
> MAPREDUCE-3251 is not a practical permanent solution for all jobs.  
> Especially for tools like pig where they are not aware of 
> mapreduce.job.am-access-disabled and may deal with it properly.
> We should add in a config option that would allow someone to restrict the 
> range of ports that the MR-AM can bind to.  It will slow down startup in some 
> cases because we will have to probe for open ports instead of just asking the 
> OS to find one for us.  But we can make that conditional on this config so 
> users who do not set this config do not see any performance degradation. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to