Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 6 Feb 2012 01:39:59 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <916074335.572.1328492399723.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1282936381.139.1328476919338.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3810) MR AM's ContainerAllocator is
 assigning the allocated containers very slowly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli updated MAPREDUCE-3810:
-----------------------------------------------

    Status: Patch Available  (was: Open)

Patch summary:
 - Mostly moving log statements in the heartbeat critical path to debug level
 - Added equals/hashCode for priority for faster lookup (the default impl uses getProto() which becomes costly) and improved comparesTo() in ResourceRequest.
                
> MR AM's ContainerAllocator is assigning the allocated containers very slowly
> ----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3810
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3810
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: mrv2, performance
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Vinod Kumar Vavilapalli
>            Priority: Blocker
>             Fix For: 0.23.1
>
>         Attachments: MAPREDUCE-3810-20120205.txt
>
>
> This is mostly due to logging and other not-so-cheap operations we are doing as part of the AM->RM heartbeat cycle.

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