You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Ostap (JIRA)" <ji...@apache.org> on 2014/01/21 13:32:19 UTC
[jira] [Created] (OOZIE-1673)
"oozie.launcher.mapred.job.queue.name" as global property for oozie
Ostap created OOZIE-1673:
----------------------------
Summary: "oozie.launcher.mapred.job.queue.name" as global property for oozie
Key: OOZIE-1673
URL: https://issues.apache.org/jira/browse/OOZIE-1673
Project: Oozie
Issue Type: New Feature
Affects Versions: 4.0.0
Reporter: Ostap
Assignee: Ostap
Currently, if not queue or a custom queue is set for an action, the launcher job will use the same queue.
This leads to a deadlock situation in small clusters where all slots are taken by launcher jobs that cannot progress because there are not slots avail.
That could be prevented by setting oozie.launcher.mapred.job.queue.name=launcherqueue. Now we should add this to every action configuration, but there no way to specify this globally.
The easiest solution is to add property "oozie.launcher.mapred.job.queue.name" to oozie-site.xml and add it to every launcher config if exists.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)