Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sat, 22 Oct 2011 06:20:32 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (Reopened) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <809848724.4444.1319264432380.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1451821500.16114.1319129951146.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (MAPREDUCE-3234) Locality scheduling broken due
 to mismatch between IPs and hosts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli reopened MAPREDUCE-3234:
------------------------------------------------

    
> Locality scheduling broken due to mismatch between IPs and hosts
> ----------------------------------------------------------------
>
>                 Key: MAPREDUCE-3234
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3234
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Priority: Blocker
>         Attachments: MR-3234.1.patch
>
>
> I noticed that, on a single-rack cluster, I wasn't getting hardly any data locality. The issue appears to be the code in RMContainerAllocator which changes the resource requests to use IP addresses instead of hostnames:
> {code}
>            //host comes from data splitLocations which are hostnames. Containers
>            // use IP addresses.
>            //TODO Temporary fix for locality. Use resolvers from h-common. 
>            // Cache to make this more efficient ?
> {code}
> However, at least on my cluster, the resource manager sees node resources as hostnames, not IPs. Removing this code fixed data locality.

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