[
https://issues.apache.org/jira/browse/HADOOP-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702955#action_12702955
]
Matei Zaharia commented on HADOOP-5745:
---------------------------------------
Dhruba, I think you have a bug in that reloadAllocs doesn't define
poolMaxJobsDefault as a local variable. This means that it assigns directly to
the class field when it reads that element in the XML file. This is
inconsistent with how reloadAllocs handles other settings because it means that
if reloadAllocs encounters an error in the file later, it will have set the
poolMaxJobsDefault but not the other settings. You just want to define a local
variable poolMaxJobsDefault in reloadAllocs the same way it has a local
userMaxJobsDefault.
> Allow setting the default value of maxRunningJobs for all pools
> ---------------------------------------------------------------
>
> Key: HADOOP-5745
> URL: https://issues.apache.org/jira/browse/HADOOP-5745
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fair-share
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: fairShareMaxJobs.patch
>
>
> The <pool> element allows setting the maxRunningJobs for that pool. It wold
> be nice to be able to set a default value for all pools.
> In out configuration, pools are autocreated.. every new uesre gets his own
> pool. We would like to allow each user to be able to run a max of 5 jobs at a
> time. For the etl pool, this limit will be set to a greater value,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
