hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10281) Create a scheduler, which assigns schedulables a priority level
Date Tue, 12 Aug 2014 01:08:12 GMT

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

Hadoop QA commented on HADOOP-10281:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12661094/HADOOP-10281.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-common-project/hadoop-common.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/4450//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/4450//console

This message is automatically generated.

> Create a scheduler, which assigns schedulables a priority level
> ---------------------------------------------------------------
>
>                 Key: HADOOP-10281
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10281
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Chris Li
>            Assignee: Chris Li
>         Attachments: HADOOP-10281.patch, HADOOP-10281.patch, HADOOP-10281.patch, HADOOP-10281.patch
>
>
> The Scheduler decides which sub-queue to assign a given Call. It implements a single
method getPriorityLevel(Schedulable call) which returns an integer corresponding to the subqueue
the FairCallQueue should place the call in.
> The HistoryRpcScheduler is one such implementation which uses the username of each call
and determines what % of calls in recent history were made by this user.
> It is configured with a historyLength (how many calls to track) and a list of integer
thresholds which determine the boundaries between priority levels.
> For instance, if the scheduler has a historyLength of 8; and priority thresholds of 4,2,1;
and saw calls made by these users in order:
> Alice, Bob, Alice, Alice, Bob, Jerry, Alice, Alice
> * Another call by Alice would be placed in queue 3, since she has already made >=
4 calls
> * Another call by Bob would be placed in queue 2, since he has >= 2 but less than
4 calls
> * A call by Carlos would be placed in queue 0, since he has no calls in the history
> Also, some versions of this patch include the concept of a 'service user', which is a
user that is always scheduled high-priority. Currently this seems redundant and will probably
be removed in later patches, since its not too useful.
> ----------------
> As of now, the current scheduler is the DecayRpcScheduler, which only keeps track of
the number of each type of call and decays these counts periodically.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message