hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2652) MR-279: Cannot run multiple NMs on a single node
Date Wed, 31 Aug 2011 10:49:09 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vinod Kumar Vavilapalli updated MAPREDUCE-2652:

    Attachment: MAPREDUCE-2652-20110831.txt

The latest patch looks good mostly. +1 overall.

Updating patch with very minor changes, hope that's fine.
 - Modified MiniMRYarnCluster to start shuffle on 8083 (non-default value).
 - Replaced 8080 with a constant DEFAULT_SHUFFLE_PORT and renamed SHUFFLE_PORT to be SHUFFLE_PORT_CONFIG_KEY
 - Fixed a few log messages and wrapped around a couple of lines longer than 80 chars.

Will commit this once Jenkins blesses it.

> MR-279: Cannot run multiple NMs on a single node 
> -------------------------------------------------
>                 Key: MAPREDUCE-2652
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2652
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>             Fix For: 0.23.0
>         Attachments: MAPREDUCE-2652-20110831.txt, MR-2652-trunk-v3.patch, MR-2652-trunk-v4.patch,
MR-2652-v1.txt, MR-2652-v2.txt
> Currently in MR-279 the Auxiliary services, like ShuffleHandler, have no way to communicate
information back to the applications.  Because of this the Map Reduce Application Master has
hardcoded in a port of 8080 for shuffle.  This prevents the configuration "mapreduce.shuffle.port"
form ever being set to anything but 8080.  The code should be updated to allow this information
to be returned to the application master.  Also the data needs to be persisted to the task
log so that on restart the data is not lost.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message