hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4428) Job Priorities are not handled properly
Date Thu, 16 Oct 2008 14:21:45 GMT

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

Vinod K V commented on HADOOP-4428:

I think this happens because of the set-up tasks introduced in HADOOP-4261.

Earlier, jobs were initialized and moved into the running-job's queue in the order of their
presence in waiting-jobs' queue which is by priority (and more).

Now, even though jobs are initialized according to their order in waiting-jobs' queue, depending
on the time taken for successful return and reporting of set-up tasks. jobs may be moved out
of order into the running-jobs' queue(a linked list). Also, JobTracker launches set-up tasks
of initialized jobs in the order of its own jobs TreeMap data structure which stores jobs
in the order of JobIDs. I think the later combined with the former explains the behavior explained
by Karam.

> Job Priorities are not handled properly 
> ----------------------------------------
>                 Key: HADOOP-4428
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4428
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>    Affects Versions: 0.19.0
>         Environment: Cluster:  106 TTs  MapCapacity=212, ReduceCapacity=212
> Single Queue=default, User Limit=25, Priorities = Yes.
> Using hadoop branch 0.19 revision=705159 
>            Reporter: Karam Singh
> Job Priorities are not handled properly 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message