[
https://issues.apache.org/jira/browse/OOZIE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ostap updated OOZIE-1673:
-------------------------
Description:
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.
The problem is that we cannot specify the queue name on Oozie server. Each
Oozie workflow job has to define its launcher job queue name
(oozie.launcher.mapred.queue.name). If user didn’t specify this parameter in
oozie’s job property, the “default” queue would be used for Launcher job,
resulting in potential deadlock situation.
We need to add a feature to Oozie so that it can take “oozie.launcher.xxx”
parameter from oozie-site.xml so that user’s oozie job property doesn’t have to
specify this parameter.
was:
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.
The problem is that 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.
> "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.
> The problem is that we cannot specify the queue name on Oozie server. Each
> Oozie workflow job has to define its launcher job queue name
> (oozie.launcher.mapred.queue.name). If user didn’t specify this parameter in
> oozie’s job property, the “default” queue would be used for Launcher job,
> resulting in potential deadlock situation.
> We need to add a feature to Oozie so that it can take “oozie.launcher.xxx”
> parameter from oozie-site.xml so that user’s oozie job property doesn’t have
> to specify this parameter.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
