You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2011/08/05 00:03:27 UTC
[jira] [Created] (OOZIE-9) Launcher job should be able to run in
different queue than job itself
Launcher job should be able to run in different queue than job itself
---------------------------------------------------------------------
Key: OOZIE-9
URL: https://issues.apache.org/jira/browse/OOZIE-9
Project: Apache Oozie (Incubating)
Issue Type: Bug
Reporter: Alejandro Abdelnur
Assignee: Alejandro Abdelnur
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.
The solution is to allow launchers to use a different queue (i.e. oozie.launcher.mapred.job.queue.name=launcherqueue).
This can be done today, but if the action defines a custom queue (i.e. mapred.job.queue.name=fooqueue) the above property is overwritten and both launcher and job end up in the same queue.
The JavaActionExecutor should do a special check.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-9) Launcher job should be able to run in
different queue than job itself
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086696#comment-13086696 ]
Alejandro Abdelnur commented on OOZIE-9:
----------------------------------------
Patch available at: https://github.com/tucu00/oozie/commits/AOOZIE-9
> Launcher job should be able to run in different queue than job itself
> ---------------------------------------------------------------------
>
> Key: OOZIE-9
> URL: https://issues.apache.org/jira/browse/OOZIE-9
> Project: Apache Oozie (Incubating)
> Issue Type: Bug
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
>
> 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.
> The solution is to allow launchers to use a different queue (i.e. oozie.launcher.mapred.job.queue.name=launcherqueue).
> This can be done today, but if the action defines a custom queue (i.e. mapred.job.queue.name=fooqueue) the above property is overwritten and both launcher and job end up in the same queue.
> The JavaActionExecutor should do a special check.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OOZIE-9) Launcher job should be able to run in
different queue than job itself
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur resolved OOZIE-9.
------------------------------------
Resolution: Fixed
integrated
> Launcher job should be able to run in different queue than job itself
> ---------------------------------------------------------------------
>
> Key: OOZIE-9
> URL: https://issues.apache.org/jira/browse/OOZIE-9
> Project: Apache Oozie (Incubating)
> Issue Type: Bug
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
>
> 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.
> The solution is to allow launchers to use a different queue (i.e. oozie.launcher.mapred.job.queue.name=launcherqueue).
> This can be done today, but if the action defines a custom queue (i.e. mapred.job.queue.name=fooqueue) the above property is overwritten and both launcher and job end up in the same queue.
> The JavaActionExecutor should do a special check.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira