hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4428) Job Priorities are not handled properly
Date Tue, 21 Oct 2008 05:58:44 GMT

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

Owen O'Malley commented on HADOOP-4428:

I'd argue that we must look at jobs in the same queue.
  1. The setup task is user code, and therefore could take an hour to run. It is unacceptable
to completely block the queue while a job is being setup.
  2. We would need to prevent a huge number of jobs being setup at the same time, so we should
set a cap for how many jobs can be initialized at once. (3 jobs / user and 10 jobs for all

 Further, we must keep the running jobs sorted by priority and submit time, just as the waiting
list is. The fact it is not, is also a blocker.

> 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
>            Assignee: Vinod K V
>            Priority: Blocker
>             Fix For: 0.19.0
>         Attachments: HADOOP-4428-20081017.1.txt, HADOOP-4428-20081020.txt, HADOOP-4428.patch
> 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