hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3211) Fetch failures if used ephemeral port for property "mapreduce.shuffle.port".
Date Wed, 19 Oct 2011 13:46:11 GMT

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

Hadoop QA commented on MAPREDUCE-3211:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12499677/MAPREDUCE-3211.patch
  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 applied patch does not increase the total number of javac compiler warnings.

    -1 findbugs.  The patch appears to introduce 160 new Findbugs (version 1.3.9) warnings.

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

    +1 core tests.  The patch passed unit tests in .

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

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1068//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1068//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1068//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1068//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-app.html
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1068//console

This message is automatically generated.
                
> Fetch failures if used ephemeral port for property "mapreduce.shuffle.port". 
> -----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3211
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3211
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: job submission, mrv2
>    Affects Versions: 0.24.0
>         Environment: Linux
>            Reporter: Prashant Sharma
>            Assignee: Prashant Sharma
>              Labels: ShuffleHandler
>             Fix For: 0.24.0
>
>         Attachments: MAPREDUCE-3211.patch, MAPREDUCE-3211.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> To reproduce the bug. 
> Use the following property in mapred-site.xml
> <configuration>
>     <property>
>       <name> mapreduce.framework.name</name>
>       <value>yarn</value>
>     </property>
>     <property>
>       <name> mapreduce.shuffle.port</name>
>       <value>0</value>
>     </property>
> </configuration>
> and following in yarn-site.xml
>   <property>
>     <name>yarn.nodemanager.aux-services</name>
>     <value>mapreduce.shuffle</value>
>     <description>shuffle service that needs to be set for Map Reduce to run </description>
>   </property>
>  <property>
> <name>yarn.nodemanager.aux-services.mapreduce.shuffle.class</name>
> <value>org.apache.hadoop.mapred.ShuffleHandler</value>
> </property>
> Then try to start the yarn daemons.
> And submit the job. (which would eventually fail).
> Also observe NM logs. It says shuffle handler service started at port 0; :P

--
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

        

Mime
View raw message