[
https://issues.apache.org/jira/browse/OOZIE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881604#comment-13881604
]
Venkat Ranganathan commented on OOZIE-1673:
-------------------------------------------
bq. I'd say that Venkat's suggestion of putting it in
action-conf/<actiontype>.xml is the correct way to do this, not the workaround.
Agreed. Also, the config-default.xml is something I did not know about.
Agreed that these should be better documented
> "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)
