Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 26 Mar 2012 08:59:39 +0000 (UTC)
From: "Steve Loughran (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <869986456.16646.1332752379680.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <739375567.6053.1332464902134.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-4058) adjustable task priority
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Loughran commented on MAPREDUCE-4058:
-------------------------------------------

seems a reasonable patch as there's no obvious cost to running the TT at a higher level than tasks. Running the DN at a higher level could give it priority over the tasks, which may hurt their throughput when the DN was under heavy external load -but does that matter?

# patch is --git not --no-prefix so jenkins can't apply
# the jenkins runs won't test this anyway; would visual review suffice, or could the tests be added to the bigtop test suite?
                
> adjustable task priority
> ------------------------
>
>                 Key: MAPREDUCE-4058
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4058
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: task-controller
>    Affects Versions: 1.0.0
>            Reporter: Allen Wittenauer
>         Attachments: MAPREDUCE-4058-branch-1.0.patch
>
>
> For those of us that completely destroy our CPUs, it is beneficial to be able to run user tasks at a different priority than the tasktracker. This would allow for TTs (and by extension, DNs) to get more CPU clock cycles so that things like heartbeats don't disappear.

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