hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4058) adjustable task priority
Date Mon, 26 Mar 2012 08:59:39 GMT

    [ 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


View raw message