[OOZIE-9] Launcher job should be able to run in different queue than job itself

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: pre-Apache
• Assignee: Alejandro Abdelnur
• Reporter: Alejandro Abdelnur
• Created: 04/Aug/11 22:02
• Updated: 02/Mar/12 22:49
• Resolved: 26/Aug/11 18:17

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.

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.