hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matei Zaharia (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5186) Improve limit handling in fairshare scheduler
Date Fri, 06 Feb 2009 21:26:59 GMT

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

Matei Zaharia commented on HADOOP-5186:
---------------------------------------

Both suggestions make a lot of sense. So, to clarify, would the logic look like this?
- For each pool, initialize and schedule at least its maxRunningJobs number of jobs.
- If all tasks from all initialized jobs in the pool are running, then initialize further
jobs.

> Improve limit handling in fairshare scheduler
> ---------------------------------------------
>
>                 Key: HADOOP-5186
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5186
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/fair-share
>            Reporter: Hemanth Yamijala
>            Priority: Minor
>
> The fairshare scheduler has a way by which it can limit the number of jobs in a pool
by setting the maxRunningJobs parameter in its allocations definition. This limit is treated
as a hard limit, and comes into effect even if the cluster is free to run more jobs, resulting
in underutilization. Possibly the same thing happens with the parameter maxRunningJobs for
user and userMaxJobsDefault. It may help to treat these as a soft limit and run additional
jobs to keep the cluster fully utilized.

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


Mime
View raw message